Why is Cargo organised as if all contributors belong to a single organization? Other languages have namespaced packaging, but not Rust? Why? It leads to name clashes. Let's say "Some Joe" creates some mediocre implementation of Base64 and creates the base64 crate. Let's say I want to contribute a b…

[image] carols10cents: Exactly, that's my point. Namespacing doesn't help with this problem. ...but that isn't the problem described in the original post. The point is that the first crate to get named something like base64 gets a significant "mindshare" advantage over every other competitor…

[image] DanielKeep: The point is that the first crate to get named something like base64 gets a significant "mindshare" advantage over every other competitor based on the name alone. I don't use libraries because of mindshare; I use libraries because they meet my needs. [image] DanielKeep…

[image] DanielKeep: The point is that the first crate to get named something like base64 gets a significant "mindshare" advantage over every other competitor based on the name alone. If you have somejoe/base64 and you/base64, there's no immediate reason to prefer one over the other. One doesn'…

[image] olsonjeffery: The impression I received from reading @carols10cents is that, implied from history of other package managers, is that users will pick the one with most relevant name 9 times out of 10 before moving on their next task. I did not intend to imply that, actually-- I encoura…

@carols10cents okay, so then would allowing slashes or some other form of nominal namespacing plus metadata serve that goal of finding the best solution to a greater extent? Is this a ux problem on crates.io ?

[image] olsonjeffery: Okay, so then would allowing slashes or some crude, nominal namespacing plus metadata surface that to a greater extent? I think projects like Awesome Rust that curate crates and aggregate quality crates for different purposes are the best solution rather than namespacing…

RRQLDR: Names matter, namespacing gives us more, better names, which means better discoverability, and minimises a source for potential non-technical bias in choosing a crate. [image] carols10cents: I don't use libraries because of mindshare; I use libraries because they meet my needs. [...] …

I totally agree, take for example the Iron repo has crates called session, persistent, cookie, and router etc. The names are so vague that you can't tell they have anything to do with Iron's middleware layer. This also means that all the other web frameworks can't use those names. At least with cond…

[image] DanielKeep: The human mind is a trecherous thing, but I suppose a robot wouldn't understand that. (Pre-emptive note: on the off chance calling carols10cents a robot doesn't make it clear, I'm being facetious. And anyway, some of my favourite people are robots; like CGP Grey.) gasp Y…

[image] DanielKeep: Names matter, namespacing gives us more, better names If we put your other arguments aside for a second, and really do consider that names matter, aesthetically "base64" is a lot more pleasing than "somejoe/base64" You seem to want to foist less aesthetically pleasing, ha…

Cargo problems - namespacing

carols10cents July 14, 2015, 3:12pm 11

I think projects like Awesome Rust that curate crates and aggregate quality crates for different purposes are the best solution rather than namespacing.

Topic		Replies	Views
Pre RFC: We need a process for giving crates to new maintainers	33	3803	January 12, 2023
Dude has ~100 empty crates with the most common names. Is that ok? community	30	4782	June 28, 2019
Should people be allowed to "reserve" crate names?	40	7940	January 12, 2023
How to guarantee the sustainability of Rust crates ?! community	30	1810	August 20, 2024
Package and crate naming convention help	23	7277	February 12, 2022

Cargo problems - namespacing

Related topics