4 ms·
I remember this incident and it is one of many reasons I was turned off by the entire JS ecosystem.
by lvl155 1y ago
I remember this incident and it is one of many reasons I was turned off by the entire JS ecosystem.
- tkiolp4 1y agoHow come this is related to JS only? Like, if I own a python/rust/go/whatever public package named XYZ and later a company named XYZ forces me to release the package because of trademark issues, and I cannot do but obey, all my packages may run the same luck, so anybody relying on them would be screwed. I don’t see how the size of the package matters here.
- another-dave 1y agoTo your point, in JVM the convention is to package based on domain name so you don't have this type of issue. But I think the GP's point is that the cultural in other ecosystems didn't lean as heavily into "there's a package for that®" as JS does
- vb-8448 1y agoI think the issue is that JS force you to have hundreds, or even thousands, dependencies. Python and other language have a richer std library and more "general purpose" packages, so the total number of dependencies is lower.