It depends entirely on the budget really. Meteor is great for turning over applications quickly, but that's it. Ember is a better frontend full stack framework and if the server is to be built by someone else, go with Ember.
If the budget is large, there's a good dev team and the project needs a performance kick then React is the better choice, if built right.
We've been handed over React codebases though that needed saving and while the previous devs might have been fairly competent, React has a lot more work involved which can make people get lazy after a while and have the opposite effect of what it was intended for, and that's speed.
For personal projects I will never go for React. I love the concept of React and how it works, but there's too much boilerplate and I personally prefer more full stack solutions.
Yet the whole world still celebrate St. Patricks day every year, the culprit who forced that plague on Ireland. I'd love to live in an Ireland that people celebrated by dancing over fires and worshipping the sun. That sounds like a much happier place. Can't we just have paganism back and detoxify ourselves of the catholic church?
This doesn't exactly stop you from doing that though. Companies that need to turn over products quickly and efficiently would benefit a lot from this but I wouldn't see myself using it for everything either.
Why wouldn't Amazon use its recently acquired c9.io as the development tool for this? Did they buy it just to drive it into the ground because activity from the staff has dropped quite a lot.
They're the clear market winner but some companies might need an internal youtube clone or might need to adapt a similar system that they would find his useful for. But hey if it has enough bells and whistles it could be the facebook to myspace.
Also an overlay or scripting app, memory address reading or an MITM attack are all much better approaches. Still pointless posting it here though.