Node+JS Interactive

JavaScript is an openly standardized programming language, but what does that mean and how does it work? This talk will provide a brief introduction to Ecma, the standards body home to the JavaScript specification and its standardization efforts, what it means to create and implement open standards, and describe TC39’s role and impact on the world of web standards. We’ll also take a look at the future of web standards, and how the process is evolving to fit the needs of modern developers.

TC39 as a committee has a long history with amazing high points, and a couple of lows as well. Over time the committee has evolved from a small group of contributors to a large gathering representing every corner of the JavaScript ecosystem. The committee’s one mission is to deliver incredible JS language features for the whole community, without breaking the web. Come hear from TC39 delegates (members) about the complexities of evolving the ECMAScript programming language, how the TC39 process works, and how TC39 is working to involve the community. Opportunities will be available for the audience to submit questions for the committee.

Modules were first standardized in ECMAScript 6 in 2015. As of December 2017, you can now use ESModules (ESM) in 3 out of 4 of the major browsers. Node.js has traditionally shipped an implementation of Common.js (CJS), you use it in your Node.js code today via require. There are vast differences between the two module systems that make it quite difficult to utilize Common.js code in an ESModule and vice versa. Implementing modules correctly in Node.js will have a significant impact on the future of JavaScript, the wrong decisions could cause fractures in the ecosystem. This talk will dive into some of the more nefarious edge cases and the ways the Node.js project has navigated them. The talk will also look into joint efforts with the Web platform as we attempt to find a single pattern that can work on both the client and server.