The last point the op makes is that you don't need a nodejs framework if you're using backbone/angular/ember. I've consistently used Socketstream combined with Ember in my for-fun projects, and it's extremely easy to build use. Combine that with the massive fun I'm having pushing events to the client from node and watching ember observers adjust accordingly, wonderful things can happen.<p>On topic - Socketstream is actively being developed and is pretty damn awesome (not to mention easy to pick up). Meteor and TowerJS turned me away when I saw the amount of rigidity in their implementations, whereas SS allows you to plug modules in and out of the framework with ease.
Nice article, and really stresses the tradeoff between flexibility/control and development time. Being control freaks, we use plain old Express at tldr.io , it's true that you need to tie everything yourself but in the long-run I think we actually save time by knowing exactly what we do and why we do it.
Does Node really scales better than other solutions with blocking operation ? ( read/write files, read/write from synchronous dbs ,etc... ) , i understand it works quite well with queue messaging or async databases ,etc ...
But is it really better when one uses it for "classic" CRUD websites that display webpages and get their infos from , a postgres database ?