📡 TRANSMISSION #16: Help pick topics

[pauldowman]

It’s time to plan TRANSMISSION show #16!

I will be talking with MDG team members about whatever the most interesting topics have been for the last month or so, and I’d like to get your help with that.

Reply here and let us know which recent topics are the most important to you!

---

Update

On Episode #15 we talked about community involvement (as usual), Meteor 1.4.2, GraphQL subscriptions, and the grapher package.

---

About TRANSMISSION

TRANSMISSION is a monthly show covering the most important topics to come out of the Meteor Forums. Each month we need your help to pick the most relevant forum posts for us to discuss with MDG in deeper detail.

Podcast Site: https://transmission.simplecast.fm/
Youtube: https://www.youtube.com/playlist?list=PLTUf4ytkmI8Q7cbf4J6aQEYun5g8fxt9B

[jamesgibson14]

Meteor Scaling - Redis Oplog [Status: Prod ready]

Update: Release: https://github.com/cult-of-coders/redis-oplog How this whole topic started: Recently I’ve been studying in depth how publications/subscriptions actually work and what I found was a fractal of bad design for scaling. But it’s very ingenious at the same time. Instead of oplog, use redis as our “oplog”. Each insert/update/remove we do in a Mongo.Collection at app level, will be pushed to redis as well. Each publication will “subscribe” to redis’ changes and update the local co…

and

Vue as the base of Blaze 2.0

Originally posted there by @aadams: Thinking ahead to Blaze 2.0, I think we should be talking about somehow building off of Vue 2.0 #128 (comment) instead of duplicating efforts or talking ourselves in circles feature after feature, and getting sidetracked or bogged down. We need to be looking at the big picture. Vue has the momentum in the broader JS community. Vue has the features we’ve been asking for and need. Vue has the performance. Vue has developers working full time on the project.…

[dbx834]

And, this:

Announcing meteor-desktop

Hello Everybody in case anyone is interested I have just released a beta version of my project called meteor-desktop. https://github.com/wojtkowiak/meteor-desktop It is an Electron integration that allows you to build a desktop client. It features: full offline support HCP built-in integration (works the same way like in Cordova, stores version on disk, has a faulty version recovery etc) modular architecture plugins support Meteor.isDesktop feature Squirrel auto update suppo…

[fhaller75]

an update on:

Apollo + Meteor: which features exactly are coming in 1.5?

Yeah so while the Blaze discussion is obviously important, I’m still really interested in what we can expect with regards to React + Meteor + Apollo integration in 1.5, as that’s probably where a large number of users are going to attack this from. What are we likely to see to make integration with Meteor easier? Anything? Because currently I feel like while the data-loading is beautiful and easy… Mutations, Optimistic UI, subscriptions, etc are all way, way, waaaaay harder to do than in Meteor…

and maybe a word about:

Electrode.io like Meteor from WalmartLabs?

This is interesting project like MeteorJS, have anyone tried? I didn’t see any discussion here. http://www.electrode.io/

[funkyeah]

Possible topics:

The impact of the loss of Arunoda/Kadira as creators/maintainers on some of the most used Meteor packages. Will those packages be removed from the guide? Any discussions with Arunoda?

As MDG transistions to a role of fostering a community developed platform where does the line of that get drawn? E.g. as Blaze gets decoupled it really is no more significant to core than Flow-router, Collection2, and other packages that are very commonly used. Should the resources spent fostering the community be put only towards what is or was in core or should it be focused on what has the most impact on the community?

[pauldowman]

Great picks for topics, thanks everyone!

[ramez]

@pauldowman
Thanks for spearheading this!

@sashko made a comment in one the posts that a number of thought leaders in Meteor have moved on. My take is that many were service providers who were needed when Meteor was still not as stable, and / or who moved on to ‘shiny’ frameworks. Now that Meteor is stable, I am noticing quite a few companies actually using it, but they are not that active in the community (i.e. forum) - they come in every once in a while to read about updates but that’s it. I can sense why, they are not necessarily looking to sell their services, they have a product that makes money (we fall into that category) and are perfectly happy about Meteor the way it is.

This is a major change in Meteor’s community composition. There is a larger “silent majority” now. I think it is an important topic to address as the community in this forum is still judging meteor by the previous composition of the community, which has evolved quite a bit.

Sorry for rambling

[batist]

Now that Meteor is stable, I am noticing quite a few companies actually using it, but they are not that active in the community (i.e. forum) - they come in every once in a while to read about updates but that’s it. I can sense why, they are not necessarily looking to sell their services, they have a product that makes money (we fall into that category) and are perfectly happy about Meteor the way it is.

Exactly! I mean, I’m getting recruiter emails with offers for Meteor jobs - trough LinkedIn… how more established can a framework be!

@pauldowman I would love to have @benjamn on, to thank him for the awesome work on 1.4.2, and to talk about what’s on the roadmap. (& can you gift him a beer for me? I’ll send you some BTC )

[ucokfm]

+1 on how official Apollo integration on Meteor 1.5 look like. Would it be like current community solution by proxying request to express server?

[ramez]

can you gift him a beer for me?

Heck, why not a bottle of wine, I’ll paypal it! Or even a Christmas basket to thank all the great MDG people.

[nicholasbydesign]

Server side rendering, future of Blaze, Vue JS as view layer.

Flow Router.

[orcprogramming]

What about Service Workers support out of the box in Meteor? It would allow us to build Progressive Web Apps (Push notifications, offline support, launch app from home screen, …)

Checkout:

https://developers.google.com/web/progressive-web-apps/

https://joreteg.com/blog/why-i-switched-to-android

[pauldowman]

Thanks everyone, it’s up now!

Great suggestions, we couldn’t fit all of them in but we tried! I’d love to hear any feedback for future shows either here or via direct message.

Thanks again to @sashko and MDG for making this possible, it’s great to have the chance for us to ask questions and hear from them directly.

Paul

[pauldowman]

Oh, and I’m going to be in San Francisco in January, I’ll buy @sashko a beer for you all.

[carina]

Thanks for all the great info, @pauldowman and @sashko! I posted my notes from the show as a written reference, hope it’s helpful.

Transmission #16 notes

I watched Transmission #16 last night and wrote up notes as a written reference. There was a lot of good info for people who have been asking questions about the direction of Meteor. Please take these notes as general gist, and if you want to know what they actually said just watch the video.

[funkyeah]

Thanks guys, and thank @carina, notes like these are super helpful if you don’t have time to watch the whole video.

[sashko]

Yes! Thank you for taking notes - I know people have mentioned not having time to listen to the whole thing before.

[sabativi]

Hello,

Just curious when the next transmission will be…
Really in love with this podcast ! Thanks for the good work, help a lot.

[sashko]

We’re in the process of scheduling the next one, now that everyone’s back from various vacations!