4 ms·

> one year is a very long time in rust land That's the problem and stabilization doesn't solve it. Only rejecting language changes will.

• nindalf 6y ago
  > nothing would compile without the nightly toolchain. This problem is solved though. Almost all nightly users shifted to stable after async-await was stabilized. The last holdout (IIRC) was Rocket, which also compiles on stable now. I can't think of any popular libraries or frameworks that require nightly. I can't think of any popular feature that people would want to use nightly for. I think you could learn Rust now, write your code and then not worry about any new features that are added, ever. Your code will work without breaking. Keep upgrading the compiler every 6 weeks and your code still won't break. That's a guarantee.
  • ezekiel68 6y ago
    Rocket should _soon_ not need nightly, but the documentation for currently available releases from github states that it still does[1]. (The compiler is ready, but the code/cargo.toml hasn't yet caught up) [1]https://rocket.rs/v0.4/guide/getting-started/#installing-rust https://rocket.rs/v0.4/guide/getting-started/#installing-rus...
• yjftsjthsd-h 6y ago
  > That's the problem and stabilization doesn't solve it. Only rejecting language changes will. What are you using, then; COBOL!? The C standard was last bumped in 2018, C++ is more aggressive than that, Python his shipped some downright controversial changes in the last minor versions, Go is gearing up for 2.0... Languages evolve.
  • clktmr 6y ago
    I am using C and Go and I don't remember ever having to deal with some kind of change in the language. Sure there were changes but with very little impact on the ecosystem. Languages evolve okay, but Rust felt more like it was just right in the making.