Hmm, I'm not so sure. "NUM" is not a one size fits all solution not least because many applications require atomicity, consistency, isolation, and durability of

Hmm, I'm not so sure. "NUM" is not a one size fits all solution not least because many applications require atomicity, consistency, isolation, and durability of a database management system. Node's API has changed frequently as it has developed, breaking older code, so don't be surprised when a genius piece of code found on Github that exactly solves your problem doesn't work with your new build of Node. Most web app developers typically don't explicitly deal with any concurrency model. There is a significant difference in aptitude between the typical HN reading coder and the average peon level developers, i.e. the majority of developers worldwide. Asynchronous code is non-trivial, especially with TDD and beyond the level of expertise of the peon level developer. Huge PHP codebases also exist, and many companies will not have the resources or the inclination to make such a change. This article is also based on the assumption that most web development in the future will be real time web apps. That's quite a big assumption, ergo although "NUM" is an interesting prospect, I doubt it will become the de facto platform for web app development.