What is wrong with Node.js?
As a company that uses multiple languages in production, we like to evaluate potential problems with our technology choices to see if there is a better alternative. We will discuss the truthyness of each assertion below.
First we need to define what a “large application” is. For our purposes, a large application is one that has multiple major sections of functionality.
In production, we have yet to run into a single problem in our Node.js applications due to the lack of a strong type system.
Type safety is an interesting topic. In practice, we’ve found type safety to be both helpful when present, and unnecessary when not. More specifically, we carefully choose the language for each project to fit the task at hand.
In production, we have yet to run into a single problem in our Node.js applications due to the lack of a strong type system. That said, we use Node.js for our customer facing APIs where ease of working with JSON is more valuable than a strong type system.
A huge plus of Node.js is the community’s intense focus on developing web development tools and libraries.
Node.js will continue to be one our primary technologies for web APIs in the UI/UX layer. While its not perfect, Node.js is an excellent choice for edge of network APIs. In our experience, the Node.js community has a strong focus on web development which means that it is ahead of other technologies in this area.
While we wish there was less drama in the community, we have found any technical issues to be manageable and the benefits of Node.js (i.e. rapid development) to be substantial.
We specialize in helping professional developers, like you, expand your skill set. Our courses are focused on enabling you to learn everything necessary to use a new technology in a live, production application.
All courses are made with love in
Palo Alto, CA.
Subscribe to our newsletter