Unfortunately, there is one thing that makes me anxious about its future: the 6-week development cycles. It’s, I believe, one of the causes of an unhealthy problem: feature bloat. It’s also the cause, in my opinion, of another problem: the immaturity of the ecosystem.
and later he said
Learning materials quickly become obsolete : Programming in Rust today is entirely different than what was programming in Rust 1.5 years ago (mainly due to async-await hitting stable). Rust’s learning curve is already high enough to discourage people from learning it, the obsolescence of tutorials and guides does not help.
I personally feel those judgement are pretty unfair according to my experience during the last 1.5 years. Yes, the language introduced
await, and for that purpose
impl Traits which is the most significant changes I think. However, apart from that, I didn't see any big issues here - I have a project left behind 2 years ago and just picked up again recently, I didn't find any significant differences that make my code not working or looked outdated.
Of cause, I am still doing major refactoring but this is basically changes of the community and slightly better grammar - for example, I replaced the crate
derive-more to do basically the same thing, and
clippy now gives more advices that I need to improve my code.
Compare to another project I left behind, which is a React frontend, now it seems to be another world - the Typescript standard has been changing quickly and I have to learn a bit more to get rid of some of the warnings/errors.
So I think we have no reason to blame the 6-week development circle. It worked better than that author thought, at least for me.