3 ms·

There‘s nothing wrong with NodeJS in principle, especially when combined with TypeScript. Can you point to something specific?

• georgyo 5y ago
  For me personally, the fact that even a simple node project will have well over 1000 dependencies is a problem. Slightly more complex projects will have more than 10k dependencies. Auditing is nearly impossible. The complete lack of a standard stdlib means always relying on community packages. Also, not a complaint directly against node directly, but for the ecosystem and developers. There is not a culture of compatibility, further fueled by the fact that multiple versions of the same dependency can be included in the same code base by different dependencies. Coming from any other language were it is a goal to keep external dependencies down, nodejs is nightmare fuel.
• michaelt 5y ago
  Many people judge programming languages as not just the language, but also the tools, library, community, conventions and so on. After all, if I love Java but hate AbstractSingletonProxyFactoryBeans, I'm probably going to hate being a professional Java developer. Some would see the left-pad incident not as an isolated oddity, but as representative of the entire NodeJS ecosystem - showing a weak standard library, a culture of pulling random, unaudited code from the internet, and rats-nest dependencies.