Better Batteries

Look, every language community loves to chant "batteries included" like it's a sacred mantra. But matklad's post cuts through the marketing fluff to ask the question nobody wants to answer: what the hell does that actually mean when your "battery" is a half-maintained crate that three people depend on? The open source world has a nasty habit of confusing "ships with defaults" with "solves your problems," and this piece does the community a favor by prying those two concepts apart. The deeper issue here is the maintenance tax that comes with curating a standard library or official tooling. When you decide to include the batteries, you're signing up for a lifetime commitment to keep them charged. The Rust ecosystem knows this pain intimately — the constant churn of `cargo` subcommands, the never-ending debate about what belongs in `std` versus crates.io. Matklad's argument, as I read it, is that the real value isn't in the batteries themselves but in the *interface* you provide to them. A good default is one you can swap out without rewriting your whole app. What I find most compelling is the implicit critique of the "just add a dependency" culture that's metastasized across JavaScript, Python, and yes, even Rust. We've built an ecosystem where the answer to every problem is another package, and the result is supply chain nightmares and a generation of developers who can't write a file parser without pulling in 47 transitive dependencies. The "batteries" approach isn't just about convenience — it's about trust. Can you trust the toolchain to give you something that works, or are you on your own in dependency hell? The source article (https://matklad.github.io/2026/08/20/better-batteries.html) deserves a read precisely because it doesn't pretend there's a clean answer. The best engineering writing acknowledges the tradeoffs, and this post does that in spades. Whether you're a language designer deciding what to ship or a developer deciding what to adopt, the question of batteries is really a question about sustainability — and that's a conversation open source desperately needs to keep having.