We are also starting to plan a LIVE show this spring at Meteor HQ in San Francisco. We have Transmission fans flying in from Denver, Chicago, Toronto & Los Angeles just to be a part of the fun! Dates and details are still being worked out. Let us know if you are interested in coming out or if you have any advice for the live taping.
As always, sincere thank you all for your support and feedback!!
TRANSMISSION is a weekly podcast/vlog covering the most important topics to come out of the Meteor Forums. Each week I need your help to pick the most relevant forum posts for @sashko and I to discuss in deeper detail.
Well if we’re to visit sensitive topics, I think you should do a quick segment on census as well.
But I’d rather see that wrapped up within the first 10 minutes to make way for discussions on anything that we could benefit from in the short to mid term, say within 6 months. Things like what to expect soon, what to watch out for, how to better align with modern development tools and standards etc.
I’m not quite sure what to ask at the moment - without being too technical or specific - because there was so much communication going on lately.
What about taking this time to cover what’s going on with the broader Meteor ecosystem? It would be great if you could have prominent package authors like @arunoda, @aldeed, @mitar, @jagi, @manuel etc discuss their plans for their most popular packages.
@benstr and @sashko … seriously enjoying the podcasts! @sashko - your explanations of the MDG thought process about various topics has been illuminating. It was great to hear your perspective about what happened with Velocity.
In that same vein, I am wondering if you gents would consider a discussion of the aging version of node in meteor. What are some of the technical challenges with updating to the latest version? I hear some people say that Fibers is holding it up, but others say that isn’t it. What is the real situation with it? What are some of the benefits of the latest version of node vs v10.4 (i think) running in Meteor now. And is a node upgrade for Meteor on MDG’s mind?
This was - I think - actually briefly touched on by sashko in an earlier podcast and is also found in the overflowing github issue.
Planely: At design time of the package system it was simply forgotten to track for each package the underlying node version they run on. So with the update to node current, pretty much every package has to be re-build… mostly a logistical annoyance and improvement of the package system.
Super stoked@sashko helped line up 2 great guests for show 10. Meteor and Galaxy project managers, @zoltan and @rohit2b. The show will focus around free and paid Galaxy hosting, the business side of Galaxy and how free hosting getting axed has raised concerns for package maintainers and their demo sites.
@dinos I finally read the whole census post and PR. I totally agree with you. This was a missed opportunity and instead sounded some alarms. Luckily (and this is why I love ope source) there is time to take feedback, adjust course and still meet the requirements of both sides.
Probably the closest to this is @tmeasday. He’s been putting in a boatload of work over the last few weeks to make the docs, tutorials, and guide really stellar for Meteor 1.3. And there’s more coming after that - the docs (specifically docs.meteor.com) are probably the worst part of the Meteor experience right now, and we’re well aware of that.
I think this is something we are going to have to compromise on, because the status quo right now has serious drawbacks:
It’s impossible to find anything on docs.meteor.com with Google (go ahead, try it!)
The page is incredibly slow on mobile because of the huge volume of content
I agree that Ctrl-F is really nice to have, but I think we’re going to have to figure out a different strategy for searching. Browser search works for libraries like Underscore where there isn’t that much stuff, but for a massive framework like Meteor I think the single-page approach just isn’t working out anymore.