Let's make predictions, at what amount of active users they will realize that NodeJS is a meaningless waste of resources and will try to migrate to something else?)
But it's not. I just launched a website that handles many taxing db queries over multiple pages and I'm able to achieve ~500 requests per second on a single worker with some simple memory caching. PHP is a waste of resources in the proper sense of the terminology, thus this Ghost stuff is fundamentally better.
I don't understand. As far I've seen, NodeJS is faster than Django/Rails in approximately every scenario, and that's a large part of the reason people are switching to it.
So either you're confused about the relative performance of Node against the other most popular frameworks, or you dislike all of the most popular frameworks and have your own preference for a webapp that you're failing to mention, and that most people disagree with you on the merits of. Which is it?
That's not my case, it is a bit more complicated.)
When one asks yourself what other people in industry are doing, one would notice that, say, Facebook resorted to translate PHP into C++ and compile it into a static binary, that Google is making huge static binaries (who said Lisp images?!) from the very beginning, and other people are trying, for some not obvious reasons, make a huge blob inside a JVM.
There are a lot of reason and logic behind products like Varnish Cache, which is, basically, a thin layer on top of an OS, the way how such apps, perhaps, should be implemented.
Finally, very clever people at Google have noticed that there are much better ways to create huge static binaries than C++ and now we have Golang, which is, probably, the direction a sane person should look at for making yet another blog engine.)
My bet is that if I search github for a blog app written in go, each one of it will beat in terms of resource utilization and performance any Node-based app, for reasons that authors of nginx or Varnish Cache or Google/Facebook engineers took into account.
Oh, sure. Under this very tag I could mention that using JS outside a browser, especially on the apps that by its nature should be a tiny layer on top of an OS's services is an idea with, ironically, related to another great one - Desktop Java Apps, and both of there great ideas are somehow appear as an reflection of one another in a grotesque mirror. They never works as expected.)
There is no justification of using any VM for an (cache-able) I/O bound apps. Why do they need nginx as a front-end if NodeJs so great?)
Could the whole engine be implemented as a few nginx's modules using another ready modules?)
