I think one obvious topics would be Meteor 1.5 and more info about the code splitting stuff.
Another thing I would find interesting is hearing more about the Meteor team’s longer-term vision and hope for Meteor. Where do you see Meteor 5 years from now? What areas of the overall web development ecosystem do you guys feel are lacking the most right now? If you had all the resources in the world, what would you do with them?
I’d gladly hear about a Meteor-specific integration for Apollo which would make using Apollo with Meteor an advantage over Apollo + Whatever. We know what advantage gives us Meteor + Mongo, but will Apollo get the same level of Meteor integration or only the same amount of love as other backends?
If/when source maps in production will be a supported build option in Meteor? See this feature request from May 14, 2015
Galaxy rolled out infrastructure changes today (28th Feb) that are meant to support some exciting new features. Can we hear about these features and what’s on the road map for Galaxy in the future?
With code splitting coming in 1.5 (which is a massive achievement!!!), can we expect to see service worker support added to the road map for Meteor sometime in the future? Service Worker support has shipped in Firefox, Chrome, and Opera. Support for Microsoft Edge & Windows 10 is currently in development. Apple (Webkit/Safari) is the only hold-out.
Do you see Meteor in the future transitioning into a platform that provides the ability to create Progressive Web Apps? Here’s a checklist of what qualifies an app to be a PWA
With the faster bundler and code splitting would be nice to hear what’s next on the roadmap for meteor. Maybe optimizations for scaling to lots of concurrent connections would be nice, given the general community’s negative perceptions on meteor scalability. Would be nice to hear about that and sashko’s take on using meteor vs firebase vs websockets vs graphql subscriptions for realtime on things like ease of use, latency, scaling, cost, maintenance…