Battery packs: Let's talk about crates, baby
smallcultfollowing.com
Battery packs: Let's talk about crates, baby
1–10 of 33 posts
Re: Battery packs: Let's talk about crates, baby
#2For those struggling for context like me: this is about the Rust programming language.
Re: Battery packs: Let's talk about crates, baby
#3[deleted]
Re: Battery packs: Let's talk about crates, baby
#4Off 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.
Re: Battery packs: Let's talk about crates, baby
#5> 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.
Re: Battery packs: Let's talk about crates, baby
#6Off 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.
Futures would be less of a problem if async was implemented as effect handling instead of coloring functions - I am truly miffed about e.g. not being to use `or_insert_with` with a fallible async function. That and build sandboxing are my 2 pie in the sky dreams for a rust edition far, far away.
Re: Battery packs: Let's talk about crates, baby
#7Go ecosystems seems to choose quality over quantity (fewer higher-quality libraries) over Rust.
What seems to be causing this?
Re: Battery packs: Let's talk about crates, baby
#8The 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)
Re: Battery packs: Let's talk about crates, baby
#9Go ecosystems seems to choose quality over quantity (fewer higher-quality libraries) over Rust. What seems to be causing this?
I'd say ease of package management. You can see this with Python too.
Re: Battery packs: Let's talk about crates, baby
#10Go ecosystems seems to choose quality over quantity (fewer higher-quality libraries) over Rust. What seems to be causing this?
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.