🚦 TRANSMISSION #1: a weekly show w/Sashko broadcasting the latest from Meteor Forums

[robfallows]

P.S. we are looking for a show name too

I’ll start the name game with “OK:GO” (see what I did there ?)

[jitterbop]

I understand the interest but that’s not about meteor. In fact, it contributes to so much of the distraction. Considering the coming of 1.3, There are so many meteor specific issues to address. I’m just saying.

[benstr]

@sashko which recent topics stand out to you as something you would like to talk on?

[pauldowman]

I’d love to hear @sashko’s thoughts on Mantra.

[hwillson]

That was just my bad attempt at Meteor forum humour. For some reason I find it funny but then again my sense of humour has been skewed by years of Seinfeld re-runs …

[aadams]

How about speak in general about the true state of Meteor’s Open Source(ness). And specifically why this PR has not been accepted.

How open source Meteor really is if pull requests are not getting in?

Another example is https://github.com/meteor/meteor/pull/5680, where we get 6s -> 0.4s improvement in data processing. Which I think should be clear for anyone in Meteor world that it is a great improvement and should be released to the world as soon as possible. No more freezing UIs. I would even go and say that this is the main reason why people experienced sluggish Blaze.

Meteor current has 107 open pull requests and counting.

[sashko]

Heading to work soon and I’ll post about which threads I’d personally like to respond to. However, I’m not sure how we are going to select from all of these great suggestions.

[sashko]

Here are the top 10 posts of last month, according to Discourse:

I tried just last week, but there wasn’t as much good stuff compared to some of these. Here are the ones I’m most interested in talking about:

1. Top 5 predictions for Meteor in 2016/Mantra (I think these can be grouped into one personally)
2. JavaScript fatigue/frustration of keeping current, specifically in the Meteor world
3. Meteor meets GraphQL, and some comparisons between Meteor with DDP and Meteor with GraphQL

I think the plan is for me to select 3 and then we’ll select 3 from community suggestions?

[aadams]

Wait, how is this list above sorted (Replies/Views seem out of order)? Since it’s a weekly thing, why not most popular by week instead of month? Also, is this a live streaming thing or will it be recorded? Will you have a hotline we can call into if you’re taking on-air questions or will there be a side feed? Lastly, when will it drop?

[sashko]

Since it’s a weekly thing, why not most popular by week instead of month?

I decided to look at the most popular ones last month since this is the first episode, and there are some great threads that don’t quite fall inside the boundary of one week.

It’s sorted by Discourse’s perception of “top”, which seems to include views, replies, and perhaps some other metrics.

When I was talking to Ben, we agreed that it would be interesting to have 3 topics selected by me personally, and 3 selected by some community process. The ones above are the ones I’m personally interested in, so there should be 3 more that are selected in a different way over which I have no control.

@benstr can you clarify the process for selecting these threads so that people can be aware?

[benstr]

Yep, @sashko is on target. We are having Sashko pick 3 he finds interesting and 3 from the community. I did not mention the part about Sashko picking 3 in the original post because… I forgot sorry.

With Sashko having the ability to select his own topics gives the audience the opportunity to hear what he (MDG) is interested in and gives MDG the ability to share pertinent and timely information and/or announcements.

Sashko those are great topics

[benstr]

Also, is this a live streaming thing or will it be recorded? Will you have a hotline we can call into if you’re taking on-air questions or will there be a side feed?

Answer here: 🚦 TRANSMISSION #1: a weekly show w/Sashko broadcasting the latest from Meteor Forums

Lastly, when will it drop?

Will be recorded Friday, likely to drop late Monday.

[benstr]

Here are the topics for show #1. Thanks for all who helped pick the topics and thanks to my partner in crime @sashko .

1. Top 5 predictions for Meteor in 2016 & Introducing Mantra (grouped)
2. The state of Meteor, Parts 1 & 2
3. JavaScript fatigue & frustration of keeping current, specifically in the Meteor world
4. How open source Meteor really is if pull requests are not getting in?
5. Meteor meets GraphQL

[sashko]

Alright, time to cram overnight to get ready for this thing!

[ffxsam]

Cool, I made a topic that’s gonna get covered! Good luck, guys!

[brajt]

Just don’t let the whole show become React dominated guys.

[seba]

While there’s no specific thread for this right now, there have been a lot of questions about scalability and performance. I think it’d be interesting to hear a bit about this topic and about future plans regarding this.

[marklynch]

+1 Seba. Most of the recommendations for improving performance come from Kadira, not Meteor. Does @sashko have anything to add or do all of MDG just defer to the infinite wisdom of @arunoda

[wojtek]

+1 For Mantra. It would be very interesting to hear what MDG (or Sashko) think about it.

[chompomonim]

How about this?

Tracker 2.0 -- The Evolution of Tracker & Solutions to its Core Problems

@dinos and @jononomo and others that have found fault with forum post length, this should please. Below is my “thin forum post summary” for my “fat medium article” linked to at the bottom: THIN SUMMARY: The problem with Tracker is one thing (and by proxy, if we are being honest, the true problem with Blaze!): tracker re-runs functions many times more than they need to be re-run (which is the sole cause of Blaze rendering jankiness!). and a fair fight would be “Tracker 2.0” vs. Redux, and wh…