> I had the same experience trying to use older versions of Rust or trying to use newer versions of rustc on older crates. It doesn’t “just” work. For many of u

> I had the same experience trying to use older versions of Rust or trying to use newer versions of rustc on older crates. It doesn’t “just” work. For many of us this coming from Go, this seems like a step backwards. I have read the blogpost... and this isn't really the substance of the complaint? It is Mozilla's fault really to be honest, they should be sticking to a nightly if they want to use weird and non-standard features. I personally think the only similarly between yours and the authors' is the (supposed) unmet promises of backwards compatibility - guess what, I code in different languages (including Go) and I can see breakages regularly, mostly not due to breaking a "backwards compatible" promise but because the broken code has been always there, just not being enforced by the compiler. Specifically in Rust, the backwards compatibility promise wasn't Microsoft's "everything including undocumented features" backwards compatibility: it was only limited to documented features used properly. This can surprise people who relies on the Microsoft definition of backwards compatibility.