Battery packs: Let's talk about crates, baby (smallcultfollowing.com)

For those struggling for context like me: this is about the Rust programming language.

Off we go comparing battery packs.

Seriously though, I wish the dual futures, streams types to be consolidated first than building anything on top of the situation.

> Battery packs are meant to address one of the most common things I hear from new Rust adopters. Everyone loves the wealth of high-quality crates available on crates.io. And everyone hates having to spend a bunch of time researching and comparing alternatives.

> [...]

> One of the key ideas from battery packs is that anybody can publish one.

So now we get to research and compare alternative battery packs? I guess it could help if there's fewer of them, but I don't see why that would be.

Go ecosystems seems to choose quality over quantity (fewer higher-quality libraries) over Rust.

What seems to be causing this?

The hobbyist device maker in me took waaay to long to be certain that this is NOT about physical batteries...

(was already confident, then there's suddenly a screenshot mentioning display components)

In my opinion this will just worsen the ecosystem. Many Rust crates are already bloated with dependencies.

Sounds like a great way to get dozens of dependencies before you even write a line of code

I hope one day to coincidentally have an earworm which works as sub-headings for something I want to write about.

Everybody agrees that Rust's ecosystem is too fragmented, but I don't think that the solution proposed here will solve anything.

The most promising project to solve this problem is https://github.com/rust-stdx/stdx which is (more or less) re-creating Go's standard library in Rust.

I guess the name is intending to evoke the "batteries included" metaphor, but it seems pretty terrible to me.

If we're sticking with the crates/cargo metaphor, surely this should be called a "pallet".

Since I don't see it mentioned yet, https://blessed.rs seems to be pretty popular for finding common/recommended crates in the Rust ecosystem.

I don't think this does enough to address to supply-chain security concerns. Before I use a crate, I want some assurance that the transitive deps have had a proper security audit, and that I'm not a single "cargo update" away from getting malware installed in my machine.