DEV Community

loading...

Discussion on: Why Node.js For Web Development in 2020?

Collapse
chrstnfrrs profile image
Christian Farris

What's the biggest reason not to use Node? Why isn't it the default choice?

Collapse
alexeychang profile image
Alexey Chang Author

Hi, Christian.

Thank you for your commenting.
So, as I know, Node.js has several drawbacks as well. You know that every technologies have their own advantages and disadvantages.

The disadvantages of Node.js are:

  1. Bottlenecks of performance (This is most terrible drawback)
  2. Issue of callback hell
  3. Tooling immaturity
  4. Growing demand for experienced professionals

Anyway, I love Node.js as long as I like javascript.

Collapse
andrewbaisden profile image
Andrew Baisden

11 years ago and still immature it takes a while for things to progress. Everybody forgot about Deno already 😂

Collapse
mcartoixa profile image
Mac

Javascript is hard (cf. github.com/getify/You-Dont-Know-JS) and it requires a lot of self-discipline. If your team is not ready to accept that, I would say Node is a bad choice.

Collapse
prashanth1k profile image
Prashanth Krishnamurthy
  1. 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
  2. Single-threaded nature is not right up on everyone's alley. Frameworks and clusters mitigate this somewhat, but it is easy to block threads.
  3. (2) => CPU intensive operations are not handled as well as other languages
  4. 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
  5. 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?
Collapse
destroyer22719 profile image
Nathan Cai

Hi there! In the world of server side programming, NodeJS is extremely late to the party. Popular server side languages such as PHP, Java, ASP. Net, Ruby, etc. Were released in the 1990s to the early 2000s. Heck, PHP was released in 1994. NodeJS on the other hand, did come in the earliest as technologically possible with the release of the V8 Engine, it was still really new and released in 2009. I know I am extremely biased but NodeJS is a serious competitor to other server side languages. But starting your server all over again from scratch to another language isn't something you can do whenever you want.