I hope announcements like this show that Rust is not a fledgling little language that moves fast and breaks things anymore. It's a mature, serious competitor to well established languages like C++ and C#. This is particularly important when trying to compare the experience of using Rust to other languages in the "better C/C++" space like Zig and Odin -- these are much newer and have more rough edges than Rust.

▲

tialaramex 2 hours ago | parent | next [-]

Rust 1.0 was in 2015. Most of these languages you're thinking of out of the Handmade Community didn't even start development until around the point Rust 1.0 shipped.

In theory Odin 2027, the 1.0 release of Bill's Odin language, is scheduled for, as the name suggests, early 2027. Zig does not have an announced 1.0 schedule, and who knows for the other two famous Handmade languages.

From the rash of "C++ successor" languages a few years ago, Carbon is still being worked on, Herb Sutter's "Cpp2" seems dead or at least in a coma, Hylo is probably also in a coma, it has several "Write this text" type blog posts, dated 2025 for example...

▲

ryukoposting 31 minutes ago | parent | next [-]

As an embedded dev, it still feels a decade away, at least. Rust is perfectly usable as a lang to make a little module that links into your main project as a .a file. But, as the language for your whole embedded codebase? Forget it. I have a litany of complaints including Cargo fuckery, ecosystem neglect, lack of first-party support, excessive code size, bad documentation, and bad IR that wastes stack by creating copies on immutable moves.

Don't get me wrong, Rust is lightyears ahead of any other alleged C/C++ successor. But I work in a space where C and C++ have been the only option for the last 30 years with absolutely no production-ready alternative. It looks like that won't be changing anytime soon, which is disappointing.

	▲	afdbcreid 18 minutes ago \| parent [-]
		Rust is already used in production for embedded (although only here and there). Not all places are ready, but I don't believe it's a decade away anymore.

▲

pjmlp an hour ago | parent | prev | next [-]

From what I could understand regarding Sean Parent's last interview at ADSP, Hylo is most likely not happening at all, given the raise of AI tooling, with Dave Abrahams re-focusing into non-computing related work going forward,

https://adspthepodcast.com/2026/08/21/Episode-300.html

Cpp2 was Herb's experiment and doesn't seem to be developed much further now,

https://github.com/hsutter/cppfront/discussions/1450

Google is still quite keen in having Carbon, for the purpose of migrating existing C++ codebases, for new code there is Rust, Go, Kotlin, Java, Swift and co.

"Carbon: graduating from the experiment - NDC Toronto 2026"

https://www.youtube.com/watch?v=WJl4ftb5Fxg&t=9

▲

zamalek 2 hours ago | parent | prev | next [-]

To Odin's credit, it is used for production software that _isn't_ a toy (by the language's own authors). It is probably 1.0 quality already.

	▲	afdbcreid 2 hours ago \| parent [-]
		Zig too. But this is far from being mainstream. Rust took around 5 years I think to become accepted in major companies, and those languages are harder to justify.

▲

hiccuphippo 2 hours ago | parent | prev [-]

> other two famous Handmade languages

Jai and... C3? FilC?

▲

stusmall 42 minutes ago | parent | prev | next [-]

>I hope announcements like this show that Rust is not a fledgling little language that moves fast and breaks things anymore

I see this on here a lot on this site, but Rust hasn't been that in over a decade. Rust's devotion to post 1.0 stability is massive and has involved some interesting design choices. I started writing run in 2015(?) and only hit one breaking change in the language. It was a niche bug in a macro that was fixed later in a later release.

Just watching hackernews you see lots of news about it, but these are additive and not breaking things. I was still writing lots of mio-style async code after async await was out. You don't have to adapt new style or libraries. I used to have a joke that you could tell a codebase's age based on the error handling libraries used, but even with that it was additive. Often multiple would exist in different parts of the same code base. "Oh wow, I've gone deep on this refactor.... I'm starting to see error_chain"

▲

nicoburns an hour ago | parent | prev | next [-]

Indeed, unless you're using Safari, you're almost certainly using Rust code to read this webpage.

	▲	afdbcreid 16 minutes ago \| parent [-]
		Allegedly, there is Rust in macOS (but maybe not in iOS), so maybe it's true even if you're using Safari.

▲

Havoc 2 hours ago | parent | prev | next [-]

For me it was the inclusion in the kernel. That locks it in as here to stay

▲

stillpointlab 2 hours ago | parent [-]

I thought it got pushed back out? Wasn't there a big drama about this and Linus weighed in?

Linus is a wise operator at this point. I often see him come in like a hammer to bash down squabbling, but then he allows the situation to evolve once things quiet down. I only saw the hammer so I'm not sure what the current state is now.

▲

Mond_ 2 hours ago | parent | next [-]

Where did you hear that it got pushed back out? It's going strong as far as I can tell.

▲

stillpointlab 2 hours ago | parent [-]

I was thinking of the public clash in 2025 between Christoph Hellwig which lead to the resignation of Hector Martin, lead of the Asahi Linux project.

It looks like later, in December 2025, Rust was officially moved from experimental to official: https://lwn.net/Articles/1049831/

	▲	bilkow an hour ago \| parent [-]
		I think what Linus pushed back on was specifically "social media brigading" as a solution to internal issues: https://lkml.org/lkml/2025/2/6/1292

▲

an hour ago | parent | prev [-]

[deleted]

▲

grougnax 29 minutes ago | parent | prev [-]

[dead]