The specific point is that the evented model is not designed as a "one size fits all" solution. It's great for certain scenarios, not very good for certain others.
Basically, the original blog post tries to get to this, remarking on node.js is sold as if it was the silver bullet of web servers, that will scale to anything for anything you .
Of course, you can try to adapt most problems into something that would work in an evented model, but you have to know VERY WELL what you're doing.
IMO the solution is simple: polyglotism. Have parts of your app in node. Other parts in python. Others in ruby. Whatever works best for each specific small part :)
Node is not useless, but it's definitely not my choice to program everything and anything. Same thing with, for example, Rails :)
Basically, the original blog post tries to get to this, remarking on node.js is sold as if it was the silver bullet of web servers, that will scale to anything for anything you .
Of course, you can try to adapt most problems into something that would work in an evented model, but you have to know VERY WELL what you're doing.
IMO the solution is simple: polyglotism. Have parts of your app in node. Other parts in python. Others in ruby. Whatever works best for each specific small part :)
Node is not useless, but it's definitely not my choice to program everything and anything. Same thing with, for example, Rails :)