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)
Battery packs: Let's talk about crates, baby
21–30 of 33 posts
Re: Battery packs: Let's talk about crates, baby
#22The 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.
Re: Battery packs: Let's talk about crates, baby
#23Everybody 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.
* It is precisely what TFA goes in for: a one-stop shop (somewhat application dependent)
* It is antithetical to the "embarassment of riches" approach that Rust tried for when they delegated almost all functionality to crates - the ecosystem has proven fruitful
Oh and a third:
It seems to me that advocacy, writing good applications, or human-readable guides will do more for convergence on crate bundles than a more technical solution. I reach for the crates I know, not yet-another-framework.
Re: Battery packs: Let's talk about crates, baby
#24Earlier quoted context omitted.
Interesting. When I learned Go a while ago, it didn't have a package manager. You just pulled down master branches directly into your global GOPATH. So pulling in a dependency was a big decision and people naturally favored "batteries included" libraries. That probably still permeates the culture today.
That is the package manager. The package has a URL. You import the URL and you're done.
PS: it looks like this issue was addressed in 2019 with the introduction of Go Modules.
Re: Battery packs: Let's talk about crates, baby
#25The 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)
Reminds me of how calling wine prefixes "bottles" makes things easier to someone.
Re: Battery packs: Let's talk about crates, baby
#26Everybody 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.
Re: Battery packs: Let's talk about crates, baby
#27Re: Battery packs: Let's talk about crates, baby
#28If we're sticking with the crates/cargo metaphor, surely this should be called a "pallet".
Re: Battery packs: Let's talk about crates, baby
#29Re: Battery packs: Let's talk about crates, baby
#30For those struggling for context like me: this is about the Rust programming language.