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

[hwillson]

Topic for show #1:

Phoenix as a Meteor alternative

Lately, some of us discovered Phoenix, the framework, written in Elixir(Erlang). Why is it great? Among pros - it is fast, battle-proven, has support for multiple databases, has channels for real-time streaming. Since some of us already moved our apps to using React, we may consider switching to Phoenix. The framework was mentioned in some forum topics, so lets discuss it here. I personally want more tutorials or videos, how to make a great real-time app using channels + webpack + React, somet…

(couldn’t resist … this just never gets old )

[benstr]

I want to discuss the two articles @sacha posted recently along with the HN comments.

The State Of Meteor Part 2: What Happens Next

Part 2 of my article exploring the current state of Meteor is out: https://www.discovermeteor.com/blog/the-state-of-meteor-part-2-what-happens-next/ (In case you missed part, here it is)

[hwillson]

Now in all seriousness - just sort this forum by “Views”; The future of Blaze is pretty much the most talked about topic within the top 20 posts. So something like:

Next steps on Blaze and the view layer

Hi everyone, For those of you I haven’t met, I’m Geoff Schmidt, one of the original Meteor core developers and CEO of MDG. With Galaxy in the field now and doing great, I’ve been able to clear out a big chunk of my schedule and you can expect to see me much more active on the forums. As we start to approach the end of the year, MDG is taking a look at the Meteor stack from top to bottom and thinking about what’s next. We’re thinking about testing, routing, schemas, and more, and what should be…

[seba]

Great initiative. Maybe half an hour would be better (Does there happen enough here to fill an hour long talk each week without repeating things to much?)
Anyway, that one hour will probably save me countless other hours reading and discussing here.

It’d be great if every now and then it could be live and there’s some time for live Q&A.

[brajt]

@benstr A kingdom for subtitles.

[goatic]

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

I am doing the Guide and spinning up on the new Data Team, which is going to be all about databases, data loading, accounts, client-side state, and related topics.

I’d love to hear more about this Data Team, and MDG’s initial thoughts on where they’ll improve Meteor This might get really important for people who feel limited by the current data-layer!

[benstr]

Yes, an hour is long. I hope it is between 30 and 45 minutes.

We opted for a pre-recorded show so we would have the opportunity to prepare more and have the ability to pull in guests if possible. But a few live shows should happen too

[sashko]

I’d rather focus on recent threads than digging up the blaze thread again - there has been enough interesting stuff in the last week to make a whole show about, and I feel like it will be more interesting to keep it current.

[rgoomar]

Topics I would like to see discussed aside from what was already posted:

Introducing Mantra - An Application Architecture for Meteor

As I promised on Friday, Here’s mantra. Checkout the blog post. Or you can directly jump into: Specification: https://kadirahq.github.io/mantra/ Sample App: https://github.com/mantrajs/mantra-sample-blog-app Have a look at it and let’s discuss.

Why React/Redux is an Inferior Paradigm

I found an interesting article by Andé Staltz and want to share. I found these quotes interesting, and counter to some of the anti-Blaze arguments we’ve read on this forum: React’s community claims that React uses functional techniques heavily, however that is not true in practice. OOP, classes, callbacks, and this are commonplace, as well as imperative method calls such as dispatch, setState, etc. This also means there is no clear interface/gate for I/O and effects. I keep hearing how Rea…

Say No to Universal Apps

This is something I always wanted to talk about. In nutshell, isomorphic apps are great in concept. But they’ll lead us to a very scary point if we followed that path. I’m not saying optimizing our apps for Mobile is bad, but building mobiles apps based on our usual app is a bad idea. I’m not sure everyone will agree on this. But, I assume you’ll find this article useful. Give it a Read: Say No to Isomorphic Apps.

[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