When Node.js is the wrong tool for the job
It seems like a lot of JavaScript developers are repeating things like &quot;more people know JavaScript so you don&#x27;t have to learn a new language, which saves you time&quot;. I don&#x27;t get it. In my experience, if you find a good developer, they can pick up C#, Swift, or Go pretty quickly, and if you can&#x27;t find a good developer, the fact that they already know JavaScript is not much of an advantage.  Even if the developer you hire already knows your language, they&#x27;re going to be spending time learning your code base and how your organization works (shared repo? PRs? Feature branches? Code review? Coding standards?)<p>That, and nose.js developers seem to repeat the claim that node.js makes delivery faster… but is it really any faster than ASP.NET, Rails, Django, or Go stdlib?  Those frameworks are so fast for prototyping and delivering bread-and-butter apps as it is (and some of them let you do multithreading to boot).<p>I&#x27;m also really not interested in how things work for &quot;typical CRUD apps&quot; because those are so trivial to write in any decent environment.<p>I&#x27;m worried that node.js articles are the same kind of echo chamber that Rails articles were 10 ago.