Okay, how about this hypothetical?<p>Ask yourself if the service you&#x27;re trying to create would have been valuable, say, 4 years ago. Yes?<p>Okay, suppose you wrote it in C++ 4 years ago <i>on four year old hardware</i>? Is it still valuable? Yes?<p>Okay, now write it today in Node and run it on modern hardware. The hardware cost is the same, the service exists,  <i>and</i> it was presumably cheaper to write and maintain in Node. Is it still valuable? Yes?<p>That&#x27;s why it&#x27;s reasonable to write apps in Node.js today: the performance <i>and cost</i> are the same as doing it in some &quot;more efficient&quot; language 4 years ago, except the cost to <i>actually build the thing now in Node</i> is (much?) lower.<p>If you were okay with the hardware costs for the service 4 years ago written in C++, you should be okay with the hardware costs for the service today written in Node.<p>You can use this argument to support &quot;slow, inefficient&quot; languages for many different kinds of projects (though not all, obviously). And I&#x27;m an efficiency nut.