2 ms·
I find this varies by ecosystem. Certain ecosystems have incredibly high quality libraries on average. However ecosystems also vary in their breadth and quantit
by jpgvm 6y ago
I find this varies by ecosystem. Certain ecosystems have incredibly high quality libraries on average. However ecosystems also vary in their breadth and quantity of available libraries also so that may play into it.
I find Rust and Perl to both have very high quality libraries available. JVM/Java ecosystem has a huge number of libraries and some extremely high quality ones but also a massive number of abandoned or low quality libraries left to decades past.
The ecosystems I find troublesome are JS, Python and to a much lesser degree Ruby. Huge numbers of low quality libraries and dependency hell.
The differences seem to stem from the culture of said ecosystems. Java code is often flexible to a fault, Rust code is strictly correct and fast but with less emphasis on flexibility/ease of use. JS/Python hail from the "get shit done" culture and as such there are many half-baked libraries.
These are just generalisations. Even the ecosystems I don't enjoy working with have some very high quality libraries of course. JS has React, Python has Tensorflow, Requests, etc.
If you want to be able to rely on library code though I would go for Java/C#/Rust maybe Go if it doesn't annoy you for other reasons.
- potta_coffee 6y agoRegardless of ecosystem, I think it's important to choose packages carefully. Python may have some trash libraries but there are also some very stable and trustworthy ones. I've used Python long enough that I have a selection of libraries I know and use. Javascript / NPM land has been a lot more difficult for me. I've been writing Go a lot lately and it's a breath of fresh air in that I rarely need packages outside of the standard library, which means I simply don't need to think about dependencies very often. That might change if the type of projects I'm working changes.