NodeUp: An ES6 modules show.

[othiym23]

ES6 is nearing completion! The ES6 module system and module loader proposals are nearly finished after an immense pile of work from Sam and Dave!

• HOW do ES6 modules work?
• HOW do they compare to CommonJS and AMD?
• WHAT is all this about static analysis?
• WHY should Node adopt the new syntax?
• WILL substack hate them forever?
• WILL Node core adopt them?
• HOW does something like jspm figure into all of this?
• CAN the Node and ES6 worlds get along?

Suggested guests:

• substack
• Raynos
• Yehuda Katz
• Domenic Denicola
• Dave Herman
• Sam Tobin-Hochstadt
• Guy Bedford
• me, I guess

[dshaw]

Yes, @othiym23. Definitely you. 👍

[groundwater]

This would be fantastic; may I suggest a few topics

1. basic usage
2. how I would use es6 modules in node
3. will I have to rewrite everything?
4. what is TC39, and why do I keep hearing about them?
5. what's set in stone, what's still being debated
6. how can i help?

[visnup]

@eventualbuddha please.

[Qard]

+1

It'd also be good to mention options for transpiling from ES6 modules to CommonJS for backwards compatibility. (https://github.com/square/es6-module-transpiler)

[eventualbuddha]

I'd be interested in chatting.

[yoshuawuyts]

Very curious as to why they chose to invent a new syntax instead of adopting commonjs, and expanding on that.

[groundwater]

I had a few very useful (if not extremely blunt) discussions with @othiym23 about ES6 modules.

I learned that there are a lot of subtle problems that the authors were trying to solve, which are not obvious from the outside. I suppose until now, the only true way to learn what all these constraints were was to read the es-discuss mail list, but I think it would be great to assume nobody listening will now, or possibly ever read that list.

Many people want to know how to use the new import syntax, but I suspect just as many will want to know why it was designed the current way.

I imagine there are constraints faced by the browser stakeholders, along with the server-side stakeholders. Each cares about different things, and enumerating those concerns would be great.

We may never all agree on what the best module syntax is, but I think we can learn a lot by understanding everyones concerns in trying to solve this problem.

[rvagg]

@bmeck this would be an interesting show right now, do you have thoughts on a panel that includes you to talk about the current state and some of the possible outcomes of spec fianlisation and implementation in Node?

[bmeck]

Happy to do, but want tc39 as well. @caridy would be great if possible
On Feb 4, 2016 7:03 PM, "Rod Vagg" notifications@github.com wrote:

@bmeck https://github.com/bmeck this would be an interesting show right
now, do you have thoughts on a panel that includes you to talk about the
current state and some of the possible outcomes of spec fianlisation and
implementation in Node?

—
Reply to this email directly or view it on GitHub
#41 (comment).

[caridy]

👍

[bmeck]

@floating would love your ear to setup the time for this.

[floating]

@bmeck email incoming

[floating]

@caridy did you get the scheduling email? waiting to hear back from you about setting this up episode. thanks!

[caridy]

@floating I haven't get to that yet, but I promise that I will do it today, and I will be available on friday.