I had to maintain a node.js back-end server a few years back. It was a nightmare of dependencies. I had to hold many libraries back, because upgrading would break something.
That's not a Node.js issue, that's a whoever built it originally issue. There's no rule in Node.js/JavaScript that you have to add a ton of deps. Culturally it's popular, sure, but that shouldn't be pinned on the runtime.
Every popular language has a cultural part to it. Java was famous for its enterprisey verbose code, even if nothing in the language requires it. PHP tends the opposite way, writing organically grown underengineered messes, even if the language allows for reasonable code. Cobol has its 10 000 line single program functions.
When you choose a language, you chose to hire the programmers for it. They will have read the same blogs, seen the same examples, made the same architectural choices.
Long term, when you choose node, you get zillions of tiny dependencies.
I had to maintain a node.js back-end server a few years back. It was a nightmare of dependencies. I had to hold many libraries back, because upgrading would break something.
That's not a Node.js issue, that's a whoever built it originally issue. There's no rule in Node.js/JavaScript that you have to add a ton of deps. Culturally it's popular, sure, but that shouldn't be pinned on the runtime.
Every popular language has a cultural part to it. Java was famous for its enterprisey verbose code, even if nothing in the language requires it. PHP tends the opposite way, writing organically grown underengineered messes, even if the language allows for reasonable code. Cobol has its 10 000 line single program functions.
When you choose a language, you chose to hire the programmers for it. They will have read the same blogs, seen the same examples, made the same architectural choices.
Long term, when you choose node, you get zillions of tiny dependencies.