I've bookmarked the page and will for sure read all the comments this weekend, they look very interesting (especially yours, that I've flew over)!
That being said, I stand by my point: Short release cycles are an illustration of The Compound Effect.
> A programming language is a platform. You can't build a thriving ecosystem on top of an unstable platform. We need, as a community, to find a solution to bring calm and focus to Rust, and then we will be able to stabilize and build a great ecosystem of libraries on top of that platform.
> Short release cycles are suitable for products, as you can remove features or UI elements, and thus complexity can decrease over time. But for platforms, it means that you can only add things, as removing parts of a platform will break backward compatibility. Thus complexity may only increase over time.
I would love to see almost "empty releases" in order not to add non-essential features and thus avoid feature bloat.
But then, what is the point of short release cycles if it's not to add features? Wouldn't longer releases cycles make more sense?