What about my ideas : offline support and espacialy make SW installable (mitar even made a PR but they … just refused it … (I say that because I created a SW for meteor : https://github.com/NitroBAY/meteor-service-worker)), windows bash (linux subsystem) support, no DB support : HTTP for basic websites which don’t want DB, websockets (not for DB) for instant chat but actually especially for games (if one wants to share X,Y of a player in real time to other users), keep going on more openess (install any templating framework from npm/atmosphere), transitions : I tried a lot and they were all buggy, like if it couldn’t really implemented by Meteor, I use Flow Router, HTTP 2.
Make meteor installable as a npm module is also a great idea, do you agree that it would make deployment way easier as most server support node.js but we had to do some changes to upload Meteor to a node server ?
Apollo is a great idea.
Other things are weird : I start with a project before summer with Blaze (I look on Internet to choose between this and React/Angular and almost everyone were saying that Blaze > all) and mongodb (no choices) and today mongodb and Blaze has been almost deprecated (no support from official team for Blaze) and Apollo will replace mongodb. I agree with these moves but it was sudden, they could have give me 6 month/1 year, as I first need to end up my project, wait and learn for new techs and refactor my app. NPM integration is a great idea, deprecate Atmosphere is really stupid.
And in a more global way Meteor is missing every single new tech like if it was something incredible when it came first but now it’s old with a potential but too old for new projects : no HTTP 2, no Service Worker etc.
Please progressive web apps should be so obvious to be enabled for a framework like Meteor https://developers.google.com/web/progressive-web-apps but still it lacks HTTP2/SW
Meteor had 2 problems : openness, popularity.
openness is improving
Meteor has now 2 problems : old (some new tech are not compatible), not popular (the ecosystem is definitively way too little).
I think MDG should burn a lot of $$ to push Meteor in a virtuous circle, actually I even think they have no choice… Meteor is so great but sooooo slow. node.js felt better, when node.js was too slow, io.js has been created and finally it put pressure on node and so both has been merged. Meteor could also bennefit from such pressure