What happens when Rust's package registry wakes up with Debian's design choices? It's Freaky Friday!
Discussion
Loading...
@andrewnez
AaaaaaaAaaaaAAAAAAAAAAAAAAAAAA
@andrewnez
your blog post contains an inaccuracy.
> The current crates.io team is seven people managing over 150,000 packages.
should be:
> The current crates.io team, as of Freaky Friday, is six people managing over 150,000 packages, because one immediately said "yeah I'm not doing all that" and went off to live in the woods.
@carol goat farming does seem very appealing atm
@andrewnez I try very hard¹ not to be a "nix fixes this" person, but .. I do feel like it ticks a lot of boxes for perceived deficiencies in both ecosystems as laid out here. Which isn't to say to say it doesn't introduce some of it's own, of course..
(¹ sometimes, honestly)
@srtcd424 there was a whole nix section but it was getting really long, so saving it for a future post
@andrewnez was hoping for more of a conclusion/your opinion on where the future is going to go. As a Rust ecosystem maintainer (and former Gentoo developer, I suppose), I tend to feel the expressiveness of rolling releases grants a lot of power, and (especially combined with fairly strict application of semver) doesn't have a lot of downsides.
@djc as a casual observer, I just want the system and language package manager people to talk to each other more
@andrewnez "The maintainers of crates.io wake up Friday morning to find their registry has swapped design philosophies with Debian."
😱😱😱😱😱
@tb definitely not inspired by anyone I met at fosdem last weekend 🫣