A little while ago, Sasha Greif wrote about what went wrong with meteor. And on top of that, MDG still hasn’t solved two long standing problems: better support for NPM packages, and support for other data sources (and in particular SQL).
1.3 is about to land soon, and fixes the NPM packages support, and adds module support. More details about 1.3 in the transmission episode 6
Once that is out of the way, the top priority seems to be Reactive GraphQL, or Apollo, and it looks awesome
If successful, the Apollo project will allow Meteor to increase its adoption in two big ways:
- The project being standalone, it can be used independently of Meteor. This allows developers to start using parts of the meteor stack incrementally. Note that MDG is also splitting up the main repo by pulling out blaze, accounts, email, and then other packages into separate repositories.
- SQL support (made possible once the Apollo itself, and the Apollo SQL drivers are written) is going to attract a lot more developers. This has been one of the top requested feature for a long while. Who wants to be forced to use MongoDB ?
With those two major barriers out of the way, I can’t wait to see how Meteor adoption is going to grow.