2 ms·
> As much as everyone loves to complain about "dependency hell" in the JS/Node ecosystem, the fact that there are tons of high quality (or, at least discernible
by goatlover 5y ago
> As much as everyone loves to complain about "dependency hell" in the JS/Node ecosystem, the fact that there are tons of high quality (or, at least discernible quality) components, largely for free, is something that really didn't exist before say the mid '00s.
CPAN for Perl and Java's rich set of libraries come to mind from before the mid 2000's.
- hn_throwaway_99 5y agoActually, I think the comparison to Java is a good one. Java had a pretty good standard library in the JDK (though I'd argue the latest ES and Node versions are pretty on par), but what it really had going for it was Apache Jakarta libraries. I think pretty much 95%+ of open source Java I used at that time was Jakarta. The difference with JS is that there are actually a ton more open source libraries available in the NPM world, but there is not an overarching project to bless some of them as "standard" and high quality (though I could see some of the Deno libs changing this). Again, it's a tradeoff - there is much more choice but that requires more management. Also, FWIW, I had many more dependency upgrade nightmares in Java vs. JS, primarily because Java's nominal typing can be very unforgiving (vs. Typescript's structural typing). I still have PTSD from Jersey 1.x to 2 upgrades.