Hacker News Reader

Comment by cynicalsecurity | Hacker News Reader

Rust changes every few months. It's simply not a mature language or people behind it have no idea what they are doing.

It turns out that there are always things to improve. You can decide to ignore those improvements for 50 years too but then people generally don’t want to use your language anymore.

> Rust changes every few months.

No it doesn't.

Quite the contrary, great care is taken so that the language stay stable. "Stability without stagnation" is one of Rust core principles.

If you haven't been maintaining any Rust code, you might have the impression that breaking changes are far more common than they really are. Rust has about as many breaking changes as Go, probably fewer? (Because Go lacks an edition mechanism.)

Which means that rust doesn't have any, does it? Since existing editions will (knock on wood) never change they should never break...

Yes, except for fixing soundness bugs (very rare in the past several years) and changes to the stdlib that might interact poorly with type inference and existing code (the time 0.3.5 issue, which is a change that breaks existing code, because the existing code technically was already "broken"/exercise a future compat footgun, but these should be about as unusual).

It's not the rust of 8-10 years ago, it's quite stable as a language now, and backward compatibility is stellar.

Reply on news.ycombinator.com