Idea: The “left-pad index”, a score for Rust crates that combines small size with popularity. The goal would be to find potential candidates for additions to the standard library, or at least merging into larger crates.
-
-
On the other hand the registry is immutible, so perhaps we should just embrace not needing everything in std?
1 reply 0 retweets 4 likes -
That's great until you get append-only malware
2 replies 0 retweets 4 likes -
Yeah, I’m wary of making std bigger myself. We already have stuff in the stdlib that’s widely disliked (MPSC channels).
2 replies 0 retweets 8 likes -
I’m not sure what the solution is here. People don’t seem to like lots of tiny crates and people also don’t like big standard libraries. People talk about Go’s standard library as the gold standard but I don’t really agree; there’s plenty of junk in there too (container/).
4 replies 0 retweets 2 likes -
It's a tradeoff: "batteries included" standard libraries are nice in that an official distribution generally has a more secure software supply chain, ideally stretching all the way to distribution releases... In absence of that, I think frameworks help:https://iqlusion.blog/introducing-abscissa-rust-application-framework …
1 reply 0 retweets 1 like -
At the cost of fewer people using the standard library. no_std is getting more and more popular because people *already* think the standard library is bloated. If Rust gets a reputation for having a bloated stdlib that threatens its claim to being a systems language.
3 replies 0 retweets 2 likes -
There are already projects out there that could, but don’t, allow use of the Rust standard library because of design disagreements. The bigger the stdlib gets, the more opportunities projects will have to object to various things.
1 reply 0 retweets 1 like
But I don’t think this trumps all other concerns anymore: y’all have convinced me that keeping the number of trusted parties in a project small *is* good for security. So there is a tough tradeoff here.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.