Rapid prototyping is an easy win. The real question is how a framework holds up in production. A lot of gripe from long time users of AngularJS comes from Angul

Rapid prototyping is an easy win. The real question is how a framework holds up in production. A lot of gripe from long time users of AngularJS comes from Angular's problems in real-world production scenarios (e.g. large amount of data means two-way binding kills performance but two-way binding is what makes the prototypes so compelling; third party directives make it easy to do all kinds of things but writing your own directives can be difficult and disillusioning; etc). Basically, the important question to ask when being dazzled by impressively easy deployment demos is: is this representative of what my experience will be like developing a real-world medium to large scale production app? So far my impression of Meteor has been that it's only achieving that "simplicity" by completely ignoring problems like initial page load. Delivering a placeholder on initial page load is an anti-pattern, especially for a technology pretending it's the only "truly isomorphic" technology out there.