After joining as a co-host on the last show I am now upgrading to full host status and on the next show will be talking with MDG team members about whatever the most interesting topics have been for the last couple of weeks.
Reply here and let us know which recent topics are the most important to you!
TRANSMISSION is a weekly podcast/vlog covering the most important topics to come out of the Meteor Forums. Each week we need your help to pick the most relevant forum posts for us to discuss with MDG in deeper detail.
I’m not sure if my question/topic is relevant or not. Still asking, Does MDG have any plan launch certification program ( just like Zend framework or Oracle Java certification)? If not, Isn’t it a good idea to launch this program so that companies can easily pick up certified meteor developers?
Again my thinking can be completely irrelevant to Transmission podcast goal. If so, you can ignore it.
+1 for 1.4 / 1.5 - I’d like to know about the problems involved with upgrading node, moving Meteor to NPM, build tool, current thoughts/plans on tackling these etc.
What about trying to get Meteor Client to be more independent. Projects like https://github.com/idanwe/meteor-client-side are really a hack that could be much better. Thinking about chrome apps, extensions, electron etc… fleeing the meteor “client restarting” time waster.
Geoff mentioned a while back that meteor should become more npm’ish also in its independence to build tools. I would love to hear what we can do about that.
Apollo Client is 100% independent for exactly this reason. I think not having an official independent Meteor Client is a bit of a bummer, but putting all of the Meteor packages on NPM will help a lot with this.
I’m actually really, really interested in what Meteor 1.5 means. Benjamin mentions in the PR that it will be an NPM-installable version of Meteor and it’s packages. That sounds brilliant, but what else does Meteor envision this change bringing? Being able to npm install universal JS with a single install!? Enquiring minds want to know!
I love apollo, but this is exactly what I mean. Installing meteor from npm would be great and solve the whole “build tool” issue. Maybe provide the meteor build tool as a light weight npm alternative to webpack, rollup and others.
For what I have seen so far, it really makes sense to use meteor and apollo gradually alongside through out a business iteration cycle. If both would be on npm and integrate into all the other tools, a dream would come true.
With the eventual switch to npm, how does MDG plan to keep the easy install / get started script?
I’d hate to see the getting started instructions become:
Install node
npm install meteor
Install Python and other needed tools (I think it was @benjamn who mentioned that we might need to have Python for compiling some binary dependencies)
I’m not opposed to doing each of these things. I’m just opposed to having to do it step by step because that goes against the ease of development philosophy MDG has pushed for so long
In my mind, npm install meteor(-tools) will be something that happens at a level below the standard installation experience, which will continue to be as easy as ever.
For folks who want to experiment with different versions of Node, or use Meteor to build npm packages, an npm installable package will be more than worth the additional installation complexity.
