I posted it elsewhere, but I remember it said from my days watching the proliferation of java frameworks: If you aren't using a framework, you're building a fra

I posted it elsewhere, but I remember it said from my days watching the proliferation of java frameworks: If you aren't using a framework, you're building a framework. When I spent some time in the node.js world, I felt the same thing: there were a few attempts at frameworks, but most everybody was writing their own glue framework between microlibraries. I am convinced that it is only fun the first few times you have to do it. :) It reminds me a little of the days before server side frameworks, where people were reinventing the wheel (poorly) every project. Further, I don't think it's necessary to run and learn every single framework that comes out. If something is an order of magnitude better, it will take over the market. (Ember, Angular, and React are all an order of magnitude better than backbone.) There will come something that is an order of magnitude better than these eventually. Until then, just get stuff done. And frankly, there's no shame in continuing to render on the server until that next generation leap comes.