yap. I agree. Not interested in that tweet issue.
Productive & well-thought-out ideas, plans and directions from @sashko is all that we want. To be honest I will be giving the talk my third listen few hours later
4 Likes
Most all of the Meteor website runs on meteor with the exception of the forums.
If there is such bad blood why didnāt MDG implement their own reactive forum using Meteor to showcase the technology instead of disqusā¦ it being one of the showcase Ember apps?
In all seriousness, I wouldnāt mind a discussion on this: Why is the Meteor.install(1.3) api better than webpack in meteor?
The sole reason I turned to webpack was for 1st-class npm support, and secondarily modules support. Iāve got hot reload and code splitting working, but theyāre not as critical. Now that Meteor 1.3 supports both the first two, Iām tempted to drop webpack (just as Iāve gotten comfortable with it!) and go back to Meteor build. The less tools and dependencies, the better, as far as Iām concerned. Iām wondering what others are thinking.
7 Likes
Agreed. Or maybe a mix of both. Either way, enjoyed the first one a lot. Lookinā forward to #2 
2 Likes
I donāt think thereās any serious bad blood, and regardless I think itās important to be able to separate feelings about people and their technology. Discourse works great, regardless of what Tom Dale says on Twitter.
Either way, this is off-topic, please start a new thread if you want to talk about Discourse.
Would love to see this discussed: How open source Meteor really is if pull requests are not getting in?
13 Likes
Exactly what Sashko said. Software is built with Ember, and there is nothing wrong with this. The same is true for Meteor, great things are built and none of the Tom Daleās tweets stopped them from doing so. Since Dom Daleās tweets were talking about the validity of the business, my comments were pointing out the Ember consultancy shop in a similar vein.
He rips into Meteor all the time. Honestly, I stopped paying attention to him long ago. There is already enough hatred and angst in the world, we donāt need to have framework holy wars to add to it.
3 Likes
Yea, his mic is not perfect but seriously, itās not terrible. Itās definitely not difficult to understand him.
Though Iām sure itāll help not so fluent speaking people understand him better.
For the 60+ minute thing. I have no problem with a 60+ min podcast, as long as you indicate where the new topic starts with markers so I can jump to a new topic should I get bored.
2 Likes
Really loved the first pod cast. Finally some content which is more relaxed with long term perspectives.
Since there was a request for feedback, just two minor points:
- Would just be great if @sashko could record the voice uncompressed, i.e.in parallel via memo on iPhone & send per mail to Ben, to put together before upload. The compressed skype audio is quite hard to understand at some pointā¦ especially when itās American English, listened by foreigners
- Not sure if itās a slang thing for the western part of the US, but you guys say the word like every few words which can be quite distracting while trying to focus on the audio
I actually found it pleasant that you two where for once more losely chatting instead of sticking and rumbling down the agenda. A great personal touch
7 Likes
Hey guys just got back from a short vacation (although couldnāt stay off the forums the whole time, should fix that next time!).
@benstr I think Iām going to pick the topics about Reactive GraphQL and Meteor open source/pull requests. Hope those are exciting for you guys!
And of course Iāll dig up a much better microphone 
5 Likes
Howdy all the awesome peeps who follow this thread. @sashko and I will be recording the show later todayā¦ here are the topics we will be covering. I only picked 3 because I feel the Reactive GraphQL topic has some potential for a great convo. If you all want to see a 4th topic just reply!
4 Likes
Yes: Meteor Load-Times (Developer Experience)
- How high is that on the prio list and what efforts are done to get close to Webpacks dev experience?
(There is a thread; Iāll dig it up)
2 Likes
We can cover that on the third topicā¦ if you have another forum post, it would be great for added context on the subject.
Here you go. A plain search in the forums for āload timesā, ābuild timesā, ādeveloper experienceā would bring up much more but below the most recent one.
Without to Spam, the reason why I chipped it in: I had a long discussion with a start up today if they would drop webpack and re-join meteor with 1.3 to simplify their stack. Than the discussion turned into a ādoes it make sense instead to rather drop meteor completely because the developer experience (rebuild times) is still terribleā. Two points of discussion for you two
- What is the effort to compete on webpacks / hot module replacement / live reload developer experience? How far is it on the agenda?
- Since a substantial overhaul of the build system is quite a task: Is there any motivation (along meteors repo-split up into npm packages) to have meteor particularly serve other build tools (such as webpack) to make it easier to tune ones dev experience? Currently, having meteor and wepack work together is quite a hack (233 Replies).
6 Likes
2 hours later ā¦ we recorded all 3 topics 
we tried
13 Likes
Canāt wait for it! Hope post production doesnāt take too long 
7 Likes
Audio of Episode 2.1 is out: Reactive GraphQL will make MeteorJS relevant to every Web Developer
Thanks for the patience everyone. Hoping to get the next 2 parts out quickly.
4 Likes