The lack of namespaces on crates.io is a feature

Post by steveklabnik » Sat, Sep 12, 2020, 1:40 PM UTC

mmis1000 wrote: post #168

steveklabnik wrote: post #100

Earlier quoted context omitted.

> Is it just because NPM does and javascript is bad Not at all! In fact, npm's implementation is why some are pro, but also why some say that it's not worth it; see https://news.ycombinator.com/item?id=24444852 for some npm specific sentiment. (Incidentally, npm added scoped packages in 2015, after these decisions were made for crates.io. However, crates.io is still smaller than npm was then...) There isn't really a…

But unlike traditional namespace, that you automatically got alias to things inside the same namespace. The npm's namespace is basically just a preserved prefix, mention scoped package inside another scoped package still requires you to write full name (scope + package) or it didn't work. I don't really see a reason that you can't implement it in a flat name package manager? Something like "you can't publish a packag…

Post by steveklabnik » Sat, Sep 12, 2020, 1:46 PM UTC

The_rationalist wrote: post #170

vips7L wrote: post #155

Earlier quoted context omitted.

Why isn't Mozilla funding them?

Mozilla is progressively dropping the rust project has they doesn't have the financial resources anymore

Post by vips7L » Sat, Sep 12, 2020, 3:01 PM UTC

steveklabnik wrote: post #173

The_rationalist wrote: post #170

Earlier quoted context omitted.

Mozilla is progressively dropping the rust project has they doesn't have the financial resources anymore

Even before, while Mozilla occasionally paid some people to do some development work, including creating it in the first place, they never paid for full-time support staff, which is what this would require.

Post by kibwen » Sat, Sep 12, 2020, 4:16 PM UTC

andrewzah wrote: post #92

kibwen wrote: post #78

Earlier quoted context omitted.

> why namespaces are just -impossible- As mentioned elsewhere in here, this is a misrepresentation of the issue. The problem is that crates.io is a free, volunteer-run project with zero full-time employees who could be tasked with the drudgery of intervening in naming disputes or managing an identity layer. This is unlike GitHub and unlike "Java" (by which you probably mean Maven Central, which is operated by Sonatyp…

"could be tasked with the drudgery of intervening in naming disputes or managing an identity layer" What do these have to do with the issue of namespaces? Having namespaces would lessen naming disputes since users would be able to name their crate whatever. Any system will have disputes, so I'm not sure what the argument is here. I understand why crates uses github for identity management, but it's not ideal that peo…

Post by valenterry » Sat, Sep 12, 2020, 4:42 PM UTC

tasogare wrote: post #139

hinkley wrote: post #54

Earlier quoted context omitted.

Java was my introduction to namespacing, so I only suspected but didn't know for a long time that Java overdid namespacing. Companies change names, they merge. Sometimes they go out of business but stick around as a foundation stewarding their old projects, and you might be going to example.org for years for documentation on a com.example module. And the namespaces weren't enforced (who is going to stop me from publi…

I agree, the Java namespace system isn’t that good. In fact I hate it. First because it uses reverse DNS while common use of URL are in the opposite order. Second because the package sbu-namespace is enforced with the file system structure, which makes for crazy long names. On the other hand I really like how C# and dotnet in general handle the matter. Package namespace are separated from logical (in-code) namespace.…