🚦 TRANSMISSION #2: broadcasting the latest from Meteor Forums

benstr · February 4, 2016, 2:22am

WOW! What a “no-brainer”! TY

benstr · February 5, 2016, 3:36pm

Show 2.2 is out, Is Meteor Really “Open-Source”

tomRedox · February 5, 2016, 3:52pm

Wahoo! Now I can stop spamming refresh on PocketCast…

sashko · February 5, 2016, 7:10pm

And here’s the video!

vonwao · February 6, 2016, 12:42am

Great work, I enjoyed the first 3 podcasts.

@benstr In the opening of the first one you suggested @arunoda was strategically linkbaiting/hooking by saying “right now meteor is a mess, frankly it’s a really bad time to start a meteor project”. I disagree, and feel the impulse to protect. I don’t think he thought anything along these lines. There was a keyword: “frankly” (meaning in an open, honest, and direct manner) which you disregarded or didn’t believe.

But, objectively it is a difficult time to start a project, if only because there’s a lot of confusion and uncertainty. Sure, if you close your eyes and ears and avoid all the noise, you can move ahead easily, but there’s a lot of stress in picking the right technology. Blaze vs. React. And if you pick React there’s still no clear way to manage state, you can use Meteor’s approach or Flux or Redux, or now Mantra.

All this causes people stress and confusion. This is clear to me. And I think it’s no blame or criticism on MDG. A lot of it is the reality of the JS ecosystem. Maybe arunoda could have pointed this out better, and he’s pretty busy, and I think he’s not a diplomat or politician!

So, really don’t want to ignite another conversation about “is meteor a mess?” just want to set the record straight on what this possibly means.

arunoda · February 6, 2016, 12:55am

Ha ha. Good analysis.
Yeah. Stop debating and let’s move on with the work we have to do.

benstr · February 6, 2016, 1:01am

I totally agree with you, @arunoda and I talked to the same affect after that show was released. My point was not to bang him, or to say “I am better”, but I want to make authors aware that uneducated or less informed readers will be absorbing the information and they will take the words “Meteor is a mess” as literal as it sounds. That is something we all need to be aware when we release content. To understand how our words will come across differently to different people and make judgement calls on the words we choose to use.

To the point… A dev like Arunoda or myself, whom work with Meteor everyday. If we hear “Meteor is a mess” we would agree and could list the reasons to back it up. Then we would turn around and start our next project with… Meteor

To a dev not familiar with the reasons why we agree with that state, it looks like we are opponents to Meteor and thus they could take the statement literally and ignore Meteor as an option for their next project. When in fact Meteor would have been awesome for their project.

It is a sad truth, but we live in a world of generalization. We all need to be politically correct or at least clearer with our words.

BTW Arunoda for President

tomRedox · February 6, 2016, 6:17am

I can definitely attest to that, we started looking at Meteor seriously early December, and it has definitely been alarming to us. The Meteor veterans here would have been around for all of the “wow Meteor is awesome” type posts from the earlier days that balance all of this out, but to those of us arriving now things could look pretty bleak if you took everything that’s been written recently at face value. It’s kind of like that “it takes a lifetime to build a reputation” quote.

I’ve really tried to immerse myself in the world of Meteor for the last two months though and I can see it’s still an amazing thing and a great community, just one that’s letting off a bit of steam at present. Just perhaps be wary of how that can look to the greater programming and non-programming (managers make decisions too… shudder…) community?

benstr · February 6, 2016, 6:31am

2.3 is live - Why no Webpack in Meteor 1.3?

So sorry for the delay this week. We experimented with partial releases and decided to go back to single podcasts per week since the feedback from you all told us to go back.

More info will be provided in the new Transmission forum post.

tomRedox · February 6, 2016, 6:35am

PS: Kudos to @benstr, @joshowens, @pauldowman, @sashko, @sacha, @tmeasday and others for all the hard work on the various podcasts - those have been absolutely invaluable to me from both a learning perspective, but also in getting another view on the true state of the community/ecosystem.

benstr · February 6, 2016, 6:45am

@tomRedox thank you so much for the encouragement! And I feel the same. So many in the Meteor community have helped me level up. Happy to be a part of such a great group!

canac · February 6, 2016, 9:19pm

I’m loving these awesome podcasts! I appreciate hearing your viewpoints on the things going on in the Meteor community, and your willingness to tackle the hard questions. Keep up the great work! I eagerly await the next episode of Transmission!

sashko · February 8, 2016, 7:13am

Video for 2.3 is up!

Going to maybe try something new with the videos for episode 3 to make them more interesting compared to the audio!

intrin · February 8, 2016, 7:43am

Excellent idea and 5/5 on effort. Please make everyone use a script in the future and practice to make it seem real. The public speaking needs improvement and makes the content painful to follow.

nilsdannemann · February 8, 2016, 9:15am

Thanks so much for this podcast! Totally love it!

lai · February 8, 2016, 2:07pm

@sashko have you guys checked out the webpack 2.0 beta? They’re somewhat aligning themselves more closely to longterm JavaScript.

gist.github.com

https://gist.github.com/sokra/27b24881210b56bbaff7

webpack-2.md

# What's new in webpack 2

Work in progress... This reflects stuff until 2.0.5-beta+

## Major changes

### ES6 Modules

webpack 2 brings native support ES6 Modules. This means webpack now understands `import` and `export` without them being transformed to CommonJS:

This file has been truncated. show original

sashko · February 8, 2016, 7:21pm

Sounds great, but unfortunately then I wouldn’t have any time to write any code. One idea we had is to go through afterwards and pick out highlights, for people that don’t have time to listen to our rambling.

hwillson · February 8, 2016, 7:43pm

Wow, I don’t agree with this at all - I find the conversation flow smooth, easy to follow and the pacing to be quite balanced. Keep in mind we’re tuning in to listen to Meteor devs discuss and answer the hot topics of this forum. I want to hear honest and heart felt discussions about these topics, not scripted and rehearsed answers. The more natural the better!

sashko · February 8, 2016, 8:03pm

Yeah this is very exciting! I’m sure @benjamn has got his ear to the ground on this stuff. Either way it won’t make it into Meteor 1.3, but I’m sure there is exciting stuff ahead.

hellogerard · February 12, 2016, 8:20pm

Related to the Open Source discussion on this episode:

Dan Abramov just moved all of the rackt repos to the reactjs org, at Facebook’s urging. He explains his actions here ( https://github.com/reactjs/redux/issues/1392 ) and I think there are some parallels that could be drawn. The questions in that issue and Dan’s clarifications are interesting too.