please provide more context about what type of app you're building. searching for "ember sucks site:news.ycombinator.com" and "backbone sucks site:news.ycombinator.com" is evidence enough that this isn't a simple comparison.
I think it often is a simple comparison. Meteor & Derby, for example, are the exact same use-case - and I think in the end, one will survive the battle and the other lose steam.
People say Backbone & Angular are different use-cases, but I find so many people "graduating" Backbone and wishing they'd chosen a more robust framework. They say they want to start minimal, so they pick Backbone. You can be minimal with Angular. It's like saying "ms paint or photoshop? Well what are you trying to do?" There's only 1 or 2 people really trying to draw something in Paint, the rest "think" they want minimal, non-bloated software. The answer to the question is Photoshop.
Now, Rails v Node v Java, something like that - there are tons of questions to ask before making such a decision, there's no one-size-fits all. But I think there is a one-size in this particular case.
let me put it this way - right now, this month, im evaluating stacks for an enterprise-y amazon-y feeling thing. Say $XX million dollar budget, ~100k LOC with ~10 engineers (mostly cranky and old) for 7 months.
i'm not sure if you're freelancing an app as a sole developer, or if you're an early stage startup, or if you work on amazon.com store. and where your project is, in this spectrum, is incredibly relevant context when you're dissing a framework.
