Why do you say it's unstable?

Take async for example. You have to choose some third-party async runtime which may or may not work with other runtimes, libraries, platforms, etc.

With Go, async code written in Go 1.0 compiles and runs the same in Go 1.26, and there is no fragmentation or necessity to reach for third party components.

It is literally being changed constantly. They chose to add it to the Linux kernel but they have to build the features they need into the language as they go. It's not backward compatible like C and C++ either. Sure, there are a couple of versions you could try to pin to in Rust, but then all your libraries need to be pinned to the same version (to be fair, this last part is an assumption).

I think very nearly every assertion in this statement is demonstrably untrue.

It's not, especially the part about it being actively changed to adapt to Linux. I've heard several complaints about this already. I may have been a little harsh on the stability concerns but I stand by my assertions in general.

They’re not changing the language, they’re stabilizing new capabilities to it. Golang is stabilizing new features too in every release.

I think the relevant problem of rust to this thread is not that it's unstable (it isn't unstable!) but it can be argued that it's a moving target

Where is Rust unstable?