[joshowens]

Spoken like a true person who spent an hour investigating the platform and then moved on. All of the issues you've pointed out are solved using third-party packaging.

[alexandernst]

Please see the other replies I made. I'm aware of all those plugins, but I'm concerned about the official support they (don't) receive.

[rywalker]

Heh Alex — the Meteor posse has arrived to this thread (I'm a big Meteor fan too!) I'll echo some of the others, that any issues with Meteor being ready for primetime don't have to do with the issues you cited, but more around being unproven to scale at high traffic (also not disproven).

I've been using Meteor since early 2013 on all my web projects, and for me the core team goes to the correct feature depth — there's 4000+ packages on Atomosphere — it'd be really hard to determine how deep they should go pulling things into the core.

[brown2rl]

Not sure what you mean by "official"? As of 0.9.0, MDG hosts all the 3rd party packages on the "official" Meteor Package Server. (https://www.meteor.com/blog/2014/08/26/meteor-090-new-packag...)

I guess you want every package to start with "mrt:"?

[roarkjs]

Why does it need to be official?

[collyw]

Plugins can and do work well some of the time. Other times they don't.

If something has been brought into the main package, its usually a sign of maturity, and stability and usefulness to a large number of people.

[joshowens]

I guess money and a degree from MIT makes the code look/smell better?