It's a bit more consistent in that no-one gets good names, but is it really such a problem that a few people happened to get in early enough that they could call their library 'fuse'?
It's a bit more consistent in that no-one gets good names, but is it really such a problem that a few people happened to get in early enough that they could call their library 'fuse'?
"rust-" or "-rs" is useless because it's on crates.io. "lib" or "-lib" similarly, unless it's part of a pair with a binary of the same name.
Here's a partial list of FUSE server implementations on crates.io:
* fuse
* cntr-fuse
* drakey-fuse
* fuse_mt
* fuser
* fuse-rs
* polyfuse
* fuse3
* yarf
Why do we make people come up with custom prefixes or opaque codenames when they could all be ~user/fuse ?A flat "top level" namespace encourages treating names, especially short names, as something with intrinsic value. You end up with the same problems that the .com namespace has, such as name squatting and first mover advantage.
Qualifying all names removes this property from names and levels the playing field. There's no value in "owning" github.com/somename/blah. Or, to take the NPM approach, @somename/blah.