Meteor is an excellent (or: the best) <i>prototyping</i> framework. Getting some idea implemented into something usable that mostly looks and feels nice is a cakewalk of a few hours (once you know a little bit about popular atmosphere packages). It also can be used to get the UX of an idea right in live-coding sessions and to give a try at the hard problems of your idea quickly (atmosphere + the giant clusterfuck of NPM stuff should contain something that does what you need more or less). If you do some small tools or or internal stuff or the like, there is no need to progress any further after prototyping.<p>If you know there will be pressure, high growth or stability/performance/predictability/maintainability requirements for years to come, by all means, use the appropriate technology to build your product. You should know where the application problems are after tinkering with a prototype in meteor. For the average "90% of current products" you'll end up building, phoenix[1] is an excellent choice to build the real stuff, and you can have the same soft-realtime-sockets of meteor with just a little more thought (but way more predictable, structured & scalable).<p>But again, IMO <i>nothing</i> beats meteor for prototyping stuff as fast as possible.<p>[1] <a href="http://www.phoenixframework.org/" rel="nofollow">http://www.phoenixframework.org/</a>