[Pre-RFC] DNS domains as package namespaces

I don't see why your own implementation would count as the fuse . Isn't the reference implementation by Linux kernel folks more deserving of being the fuse ? If your implementation isn't a fork or a drop-in replacement for the reference FUSE implementation, why would it be the fuse and not your take on it, like jmillikin_fuse ? (or something like jmfuse )

I'm having trouble parsing this, sorry. I don't think my implementation would be counted as the reference implementation, that's why it would be under my namespace and not kernel.org.

The namespace represents the identity of the author, the crate name represents its purpose. If a library's purpose is to implement the FUSE protocol then fuse is a good name for it.

This doesn't seem to be a problem on crates.io. serde_json is accepted as being for the real JSON, despite not being published as the json crate. There's http crate, but also httparse , hyper , reqwest , and a bunch of others that are arguably an implementation of HTTP, but they don't all have to be called */http .

It would sure help when trying to figure out which one to use, though. I've mostly been getting by with the json crate, but I've never been able to figure out which HTTP library is the standard so I've just used Go whenever I need to do a project that involves HTTP.