Are We 1.0 Yet?

Checking the 360 most downloaded crates of all time on crates.io to see which ones have reached version 1.0 yet.

{{ crates | map(attribute='latest_version') | selectattr('is_1_0') | list | length }} / {{ crates | length }} crates are 1.0 by now.

{% for crate in crates %} {% endfor %}

Name	Latest Version
{{ crate.name }}	{{ crate.latest_version }}{% if crate.latest_version != crate.latest_pre_release_version %} (& {{ crate.latest_pre_release_version }}){% endif %}

Why?

The Rust ecosystem is still very immature. Very few critical packages have actually reached version 1.0 yet. The semver spec says "Major version zero (0.y.z) is for initial development... The public API SHOULD NOT be considered stable." Additionally, the FAQ entry for "How do I know when to release 1.0.0?" gives some heuristics that the Rust ecosystem doesn't really abide by at all:

If your software is being used in production, it should probably already be 1.0.0. If you have a stable API on which users have come to depend, you should be 1.0.0. If you’re worrying a lot about backwards compatibility, you should probably already be 1.0.0.

I submit that it would be difficult to build a non-trivial Rust program intended for production without depending on any crates which are not yet at version 1.0.0 or higher. This situation is not really ideal. I'm not saying the maintainers of these crates are lazy, or owe the community a stable 1.0.0 release, or anything like that. I'm just saying ecosystem stability is a good thing to care about, and right now Rust in general doesn't have that.