https://www.quora.com/Which-startups-use-Meteor-in-productio...
We picked it because it enabled us to move much faster than anything we had used in the past and while it has issues that I foresee being problematic, it seems premature to optimize for them. The Meteor team is doing a great job maintaining compatibility and not forcing us developers on to make any changes to our apps as they're rolling out exciting new stuff. Granted, I did jump on when the platform was (relatively) mature late last year.
Very happy with decision so far and looking forward to building more stuff on their platform!
1. We will probably eventually need SQL
2. It might not make sense to be so JS heavy, especially since we are enterprise focused and may have to support older browsers for extended periods
3. General performance issues at scale that I would have with any new framework
Planning on solving these problems when we hit them - for now, fast is best.
Edit: They have made another good decision: seduce windows devs. Next one I believe it will be to support SQL.
They have a large and diverse fanbase, probably the most open community for newbies and the new generation of devs - the ones that come from different backgrounds - and I have also the impression that I see a larger percentage of women here than in other frameworks, that might mean something; they use the ubiquitous javascript; they promote ubiquitous computing; they have good funding; they have credible and fresh marketing; technically they are, IMHO, at least good enough. These are some of the reasons make me 'bullish' on Meteor.
IMHO, one of the often overlooked use cases for Meteor is rapid-prototyping. If anyone remembers DHH's video 10 years ago demonstrating Rails' scaffolding [0], Meteor is the 2015 version.