4 ms·
You know this is a red herring. Frequency of the release cycle is orthogonal to the amount of changes or even how long the changes are in development.
by pornel 4y ago
You know this is a red herring. Frequency of the release cycle is orthogonal to the amount of changes or even how long the changes are in development.
- pjmlp 4y agoJust wait until Rust gets 40 years old. Pity I won't be no longer around to check on it, given average human life expectancy.
- pornel 4y agoI can't wait for C++64. But "just wait until Rust will repeat C++'s mistakes" is just pure speculation. Language evolution doesn't have to make the language worse. Java, JS, C#, or Ada are pretty old now, and have been doing fine. Rust is well prepared for a 40-year lifespan with its edition system.
- pjmlp 4y agoYou quite clearly are unware of the evolution pain points to move past Java 8, .NET Framework 4.8, and how the Java community embraces Java 20, or the C# one sees C# 12, and the rate they are adding new features. As for JS, everyone knows the mess of the Web ecosystem and frontend development. Ada is doing just fine, as most vendors are still adopting Ada 2012. Ada Core and PTC are the only ones with the latest version, from 7 remaining vendors.
- pornel 4y agoBut the ecosystem lagging years behind the latest version is a separate problem, and one that ironically the 6-week release cycle of Rust helps with: there are no major upgrades to fear, and small frequent releases make the ecosystem move with the compiler instead of having time to ossify and choose to stay on an old version (the same way nobody chooses to stay on an old Chrome, but people used to stick to good'ol versions of IE and Netscape).
- pjmlp 4y agoLagging behind is only one issue, I explicilty mentioned the drama of newer updates that make many unconfortable given the rate that they now are coming with changes for the sake of it, just go read the comments on the C# 12 features announcements for a taste of it.