4 ms·
It's actually terrible, justs look at NPM and RubyGems. Instead of just coming up with a good name for your project, you have to come up with a unique one even
by hombre_fatal 6y ago
It's actually terrible, justs look at NPM and RubyGems.
Instead of just coming up with a good name for your project, you have to come up with a unique one even though the project with that name isn't even active. And since most names are taken, you have to come up with a clever one for no real reason. Or go down the route of naming strats you see on npm/gems: better-lib, lib2, lib2-better, lib3, better-lib3, etc.
It really does nobody good except for the person who was able to clutch the original name, and that's a weird incentive structure. Subreddits have this same problem where you're instantly gimped when named anything other than r/bitcoin, r/politics, r/news, r/atlanta, etc.
Instead, there should be no preciousness to names nor dictionary words. That's the correct incentive structure: none.
People keep linking https://crates.io/users/swmon https://crates.io/users/swmon and it probably seems like an easy fix to just revoke those names. But swmon isn't the problem, the system is. It's no bigger problem when swmon does it overtly vs thousands of people doing it incidentally when they register a package they don't do anything with.
The problem isn't to calibrate a system that can detect swmon but build a system where you don't care what swmon does.
What you want is something like this: https://package.elm-lang.org/ https://package.elm-lang.org/
Watching Crates get this wrong was like watching Swift not implement qualified imports.