I guess Java lost to both JS and Go because it’s ridiculously hard to deploy to Maven Central

Jan 25, 2022 · 1:08 PM UTC

8
2
1
47
Replying to @nikitonsky
Are those 442k artifacts just from Maven Central, or are other maven repos included in that number as well?
Replying to @nikitonsky
I'll sometimes have the exact version of a package in my pom.xml and the indexing is both slow and seemingly inaccurate. Worse, fetching the packages sometimes works in one IDE and not in another. I don't know if it's Maven related or a Java issue but still.
Replying to @nikitonsky
How is having fewer available libraries "losing"? What's the average quality? How many dependencies does an average project have? How many JS/Go libraries do things that the Java standard library does? And so on.
1
9
98% percent of JS libraries would not be needed if it had something resembling a half-decent stdlib and half-decent language design. Looking at isEven and shit like that.
1
2
more replies
Replying to @nikitonsky
On the other side, there's zero 'left-pad' libraries in Central
1
5
commons.apache.org/proper/co…
1
2
more replies
Replying to @nikitonsky
It’s more interesting why npm blew up with packages on day one - and pypi is struggling (comparatively), while publishing there is as easy.
2
There's arguably a much larger pool of JS programmers (*and* the set has significant overlaps with Java/Go/Python/C# etc.)
Replying to @nikitonsky
Quality>quantity :)
1
2
Not that Java libs quality was great
1
more replies
Load more