📡 TRANSMISSION #11: Help Pick Topics

benstr · April 8, 2016, 4:29pm

Howdy Meteor Forum, it’s time to plan show #11!

With 1.3 coming out we took a little break form recording shows. I hope you missed us, we missed you. So what perked your interest this week(s) in Meteor? Is there a MDG team member you want to learn more about? Have an idea how to improve the show?

Update

Show #10 was way cool, we dove into the new Galaxy offering with @rohit2b and Meteor’s new Census package with @zoltan https://transmission.simplecast.fm/10

Thank you to all the MDG project leads for being part of the show.

As always, sincere thank you all for your support and feedback!!

About TRANSMISSION

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.

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

benstr · April 8, 2016, 4:33pm

I’m thinking of grouping all the post-1.3 forum posts together and doing a wrap-up section talking about 1.3 hitting the public.

Also thinking of interviewing @sashko about being productive. I want to know his process and how he seems to be everywhere

lassombra · April 8, 2016, 4:49pm

This would be awesome, especially with regards to modules and testing which are the two big talking points of 1.3

sashko · April 8, 2016, 5:21pm

I’m excited to bring it back to basics and just have a nice chat with Ben about the forums!

hwillson · April 8, 2016, 6:35pm

No kidding! Just keeping up with the @sashko input/output I see between here and GitHub is a full-time job … then add being the Apollo lead into the mix? @benstr - find his secret, please!!!

nilsdannemann · April 14, 2016, 6:00am

Damn! I’d also be interested in this! We need his secret!

Apart from that:
If its not too late, I personally would be interested to hear MDGs current stand on their original “ease-of-use” vision. Especially in regards to the future.

I kinda liked @brajt 's this way of putting it:

When I started out with Meteor, there was a very strong “everything out of the box + just working” feel to it. Create a project and just start to code. Add perfectly fitting packages (atmosphere) and use them instantly. Deploy with one command (free tier) to present the whole thing.

Since Galaxy and 1.3 came out the overall thing feels a bit more “separated” to me.
Note: I do NOT mean worse, just different. Definitely appreciate MDGs work a ton!

Curious to hear about that.
(hope I’m not to late with this post though :D)

Anyway, great show, @benstr . Love it!

merlinpatt · April 14, 2016, 1:50pm

I’d like to see something on the Deprecation of CollectionFS.

I’d also like to hear more about Chromatic

jeffshaver · April 14, 2016, 4:03pm

updating node? why it hasn’t been updated? how to avoid getting into situations where we are forced to stay on old versions of node in the future? MDGs plan to get it upgraded? is it underway already? this issue seems pretty dead

skirunman · April 15, 2016, 10:56pm

Node update should be coming very soon, I’d guess the next release.

github.com

meteor/meteor/blob/devel/Roadmap.md



# Meteor Roadmap

**Up to date as of September 8, 2017**

This document describes the high level features the Meteor project maintainers have decided to prioritize in the near- to medium-term future. A large fraction of the maintainers’ time will be dedicated to working on the features described here. As with any roadmap, this is a living document that will evolve as priorities and dependencies shift; we aim to update the roadmap with any changes or status updates on a monthly basis.

Contributors are encouraged to focus their efforts on work that aligns with the roadmap as maintainers will prioritize their time spent reviewing PRs and issues around these contributions. This however does not mean that PRs against other features and bugs will automatically be rejected.

Items can be added to this roadmap by first getting design approval for a solution to an open issue, as outlined by our [contributing guidelines](https://github.com/meteor/meteor/blob/devel/CONTRIBUTING.md). Then, when a contributor has committed to solving the issue in the short to medium term, they can submit a PR to add that work to the roadmap. All other PRs to the roadmap will be rejected.

## Upgrade to Node 8

*Tracking pull request: https://github.com/meteor/meteor/pull/8728*

Upgrading Node will allow Meteor to take better advantage of native support for new ECMAScript features on the server, which should speed up build performance and also improve runtime performance, thanks to performance improvements in Node itself.

Perhaps even more importantly, newer versions of Node support a vastly improved debugging experience. Not only can you use native Chrome DevTools and many other debugging clients (WebStorm, VS Code, etc.) to debug your app (no more [`node-inspector`](https://www.npmjs.com/package/node-inspector)), but also the Node process runs at full speed while debugging, so you don't have to wait as long for problems to manifest themselves.

This file has been truncated. show original

hwillson · April 19, 2016, 12:40pm

@benstr @sashko … we miss you guys … Transmission 11 coming soon?

Stan · April 22, 2016, 10:38am

What about the Meteor stuff happening in What happened to MeteorPad.com? - looks like something good will come out of it.