4 ms·
> the 6-week development cycles. It’s one of the causes of an unhealthy problem: features bloat. It’s also the cause, in my opinion, of another problem: the im
by jayflux 6y ago
> the 6-week development cycles. It’s one of the causes of an unhealthy problem: features bloat. It’s also the cause, in my opinion, of another problem: the immaturity of the ecosystem.
Not sure I have the same experience or agree with that. Sure, Rust has a 6 week release cycle, but most of the time the releases are bug fixes or moving library additions into stable.
Take this release for example: the only change is ARM support on Linux and a small update to the test framework. I’d hardly describe that as bloat.
https://blog.rust-lang.org/2020/12/31/Rust-1.49.0.html https://blog.rust-lang.org/2020/12/31/Rust-1.49.0.html
> As a rust developer, I need to remain up to date with the latest developments in order not to produce code that is obsolete as soon as it’s released
Clippy should help with that, it usually flags deprecated code or better/more up to date ways of doing something. I don’t think you need to keep on top of every RFC, just use what you need.