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.
Battery packs: Let's talk about crates, baby
31–33 of 33 posts
Re: Battery packs: Let's talk about crates, baby
#32Earlier quoted context omitted.
Money dictates personal philosophies. Rust and Node have too many deps because you can't make a Patreon or Github Sponsors page for contributions to stdlib. Go is batteries-included because it was made by Google by people with a salary. The people writing "thousands of small packages are good" are the people making money from the clout of having made thousands of small packages.
What is Python?
It's probably both?
Started famously as batteries-included, until people started realizing there's money in dependencies.
I'm not a lot into Python, though. I still write a lot of it, but I don't really read or participate in its community.
Re: Battery packs: Let's talk about crates, baby
#33The 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)
Ha- same here! I was very excited to see a curated list of battery configurations/cells/wiring diagrams!