Lack of typing pushes many errors to runtime rather than compile time. Typescript has largely taken this issue off the table, but hey many people continue to use Javascript
Single-threaded nature is not right up on everyone's alley. Frameworks and clusters mitigate this somewhat, but it is easy to block threads.
(2) => CPU intensive operations are not handled as well as other languages
Dependencies - it is great to have thousands of open libraries and the dependency tree that's a mile long. But, not if you are a financial firm which deals with sensitive data
There is also dissatisfaction about all numbers being floats, consistent performance, and on and on making Node a difficult choice
Many large companies (including a few financial companies) use Node. I use Node since I can avoid the verbosity and get stuff done sooner while keeping the code base simple. Finally -
as beginners: we just try out a couple of good frameworks - ASP.NET, Fiber / Gin, a few frameworks on Node, see which of them resonate for a given problem, and just pick one up.
as enterprises: we just follow the "company-wide standards" that have been in place forever. No one ever heard of people getting fired for choosing IBM, right?
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Many large companies (including a few financial companies) use Node. I use Node since I can avoid the verbosity and get stuff done sooner while keeping the code base simple. Finally -