I looked into Meteor and it's amazing how everything clicks together. It's just such a drastic change in complexity and feels like a breath of fresh air. The one thing that made me drop it as the choice for a primary stack was the fact that it's tied so heavily into MongoDB. Meteor has a mongodb 'server' replicated client side, that's how they can actually make Meteor so god damn snappy, it's latancy compensation. If…
I've heard the sales pitch for ember and ember-cli and I've seriously begun developing with Ember for the past 2 weeks. So far, I really like the tooling around Ember but am not a huge fan of the actual framework itself. I mean, you have routers, routes, controllers, views, templates, and components - how many concepts do you need to display a ui? Maybe it's just that I can't see the forest through the trees. Perhaps…
They're dropping controllers and views in a month, with Ember 2.0. They're being replaced by components.
So really you will only work with routes and components - which should make things much easier to understand.