4 ms·
There's a secret effort in the Rust community to supplant Crates.io and create an entirely new package ecosystem with proper namespacing, security, and much bet
by echelon 3y ago
There's a secret effort in the Rust community to supplant Crates.io and create an entirely new package ecosystem with proper namespacing, security, and much better community.
Not naming names, but I know several people working to put Crates.io out to pasture.
There's a level of playing nice with them for the time being (eg. build reproducibility), but it's only KTLO.
Crates.io needs to die for Rust to thrive. They're a bungled, mismanaged liability. New code, new leadership.
- solardev 3y agoWhy does something like that need to be secret...? Isn't it in the community's best interest?
- TylerE 3y agoDrama avoidance and avoiding bikeshedding seem obvious. Much easier to present a working system than a design that will get nitpicked into irrelevancy.
- solardev 3y agoYeah, that makes sense.
- sapling-ginger 3y agoThat quite funny. Just like when some people formed a violent militant group to take down a violent tyranical dictatorship. Of course they would promise that they would absolutely de-arm right after the dictatorship has been overthrown, and immediately establish a peaceful democratic government with fair election. They absolutely would, would they? They would never turn into what they were formed to replace, would they?
- jeroenhd 3y agoCrates.io doesn't need to die necessarily. It needs some competition as a wake-up call. Once a better alternative is out there, crates.io will either wither and die or improve. If it matches its competition in terms of quality and reliability, everyone is better off. If not, the alternative solution will take over. I'm eager for this crates.io alternative to land, assuming they don't break too many projects in their improvements.
- awesome_dude 3y agoHow secret is it now that you've posted on HN about it?
- fullarr 3y agoWait I thought only I could read the secret
- fsckboy 3y agoyes, HN hides secrets automatically ******* is my password, but you can't see it. Type your password back, and I won't be able to see it. Try it!
- wyldfire 3y agoI'm not sure it's working the way you described: hunter2
- kaycey2022 3y agoIt’s working. I really can’t see it. All I see is ****
- overtomanu 3y agoMaybe you are getting tricked to give out your password...
- WJW 3y agohttps://knowyourmeme.com/memes/hunter2 https://knowyourmeme.com/memes/hunter2
- 0xfedbee 3y agotr!pt0ph@n3
- echelon 3y agoIt's an open secret.
- epage 3y agoI find this interersting as most namespacing solutions would need the cargo team involved and I've heard nothing about this.
- bluejekyll 3y agoThis was my first thought too. And there are a lot of questions that will get asked, like, will all crate library names start being prefixed as well? So you end up with use::bar; // changing to use::foo::bar; I assume the library names that can be overridden in cargo would still be accepted, and then it all gets a little messy. The transition would be very messy.
- epage 3y agoMy preferred syntax route is a new separator in package names and the lib name gets populated by everything after it. Still doesn't solve all of the policy problems with namespacing.
- csomar 3y agocrates.io is fine.