This is my biggest worry too: they essentially copied the NPM package management model and practices. Good for short term productivity, but I worry that it causes significant long-term maintainability problems.

And everything is version 0.x, in part due to technical limitations of Cargo: moving out of 0.x is a breaking change, so if you have users on 0.x (which Cargo encourages by adding semver compatibility rules which make 0.x.a compatible with 0.x.b), moving out of 0.x breaks them.

i mean yes, but at least the compiler is a tool.

While C and others are uh. Well some are finally realising they have users

Well, it seems that your point is "Firefox consists of bad code", whereas I believe that the conclusion from the post should be "The library is bad code, which is why we are not using it in production. We'd be happy to look at their rust implementation, when it's possible"

(footnote: "bad code" being an abbreviation of "100k multi-threaded C++")

@freddy

and "uses" in this case means "has it available behind a feature flag in their nightly builds, and does not ship it to normal users because of this very issue"