Anna Henningsen's guest appearances

Anna Henningsen

All JavaScript Podcasts by Devchat.tv

JavaScript Jabber

Devchat.tv Episode Roundup

Julie Ralph

Matthew Podwysocki

Brian Woodward

Jeremy Fairbank

James Shore

Craig McKeachie

Charles Max Wood

Zach Kessin

Raquel Vélez

Kassandra Perch

Glenn Block

Vitali Zaidman

Anders Hejlsberg

Joe Eames

Nolan Lawson

OwlTail

Mikeal Rogers

Arunesh Chandra

JSJ 267 Node 8 with Mikeal Rogers, Arunesh Chandra, and Anna HenningsenOn today’s episode of JavaScript Jabber we have panelists Joe Eames, AJ O’Neil, Amiee Knight and Charles Max Wood and we are talking about Node 8. To help us we have special guests Mikeal Rodgers, Arunesh Chandra, and Anna Henningsen. It’s going to be a great show. Tune in.[1:56] Is Node 8 just an update or is there more? More than just an update Two main points: Improved Prana support Native API Native APIs are helpful for Native Add-ons. For both the consumer and the developer side. Prior to update these Node Native modules ran in C++ and bound to specific to Node 8 APIs. Causes these modules to be updated or reconciled every time these modules are rereleased. Creates burden for module maintainers. Creates friction in upgrading Node versions in production departments. If you have a deployment depending on a certain Native module, some of the modules may not get updated in time when updating your Node versions. Keeping people from updating Node. Creates compatibility issues with Node users not using Node 8 Experimental support for a Native layer in Node 8 to eliminate these issues as much as possible. Important milestone for the module ecosystem. You can write extensions for Node in C++ and it decouples V8 so you can use something else on the front. Modules takes dependency on V8 API specific to a particular version. So if V8 changes your module will be extracted from that. As a side benefit, you can have another VM to take advantage of that. Major version upgrades mean updating Native modules and usually some of those modules haven’t updated to the newest version of Node and be complicated. Deep dependency wise, about 30% depends on a Native module somewhere In the future, with the Native API, you’ll be able to update Node without breaking modules. [5:51] What kind of work went into this? Most of the work was in C++ First thing that was done was, they looked at the top dependent Native modules in the ecosystem. Looked for what kind of V8 exposure they had and cataloged it Looked at how these APIs and what their purposes were Looked for a way to extract them so that they are part of Node Core Created neutral APIs, now part of the Node core. All C APIs Also has a C++ wrapper to improves usability of the API. [7:17] What’s an example of what you can do with these APIs? Native modules allows for tighter integration and better module performance Specific APIs that you can use in V8 that isn’t available through JavaScript If you have a C++ variable code and you want to expose a variable into JavaScript, that is V8 API note a Node 8 API Having it bound directly to the VM was something they wanted for a long time Google controls V8 and they bind to V8 Created a better relationship with Google starting in IOJS Also worked with Microsoft with their Node Shocker work. Same with SpiderMonkey   SpiderNode is in the works [9:23] Have you guys done any testing for performance? Some. There is a performance working group. There is a need to stay on top of V8 V8 team has focused on new language features Many features have been added over the years Many didn’t come in optimized The performance profile has changed with these features If you’re using new language features, you will see a performance boost In core, still tracking down code that was specific to the old optimizer and rewriting i to work the new optimizer  Turbo C compiler hasn’t landed yet, but is to come. Will have a completely different performance profile In most real world applications it will be faster Waiting on the release to take a version of V8 to make it easier to upgrade features in the future [11:28] Are the new features picked up from V8 or implemented in Node? It’s all in V8 Better longterm support Promises are made better in Node as a platform Added new method called util.promisify() Implementation comes from V8 Allows for more optimization for promises in Node core Promise support for the one-deprecated domains module. [13:02] Is there anything more than NMP 5? First off, delete your NMP cache. It’s in your home directory usually with a .npm extension [14:09] What are the new features in V8?Unlimited heap sizes, previously had a 4gb limit. No fixed limit.[14:09] Will you see things like chakra come out tuned for servers? Profiles of a server for application process are getting smaller Getting cut into containers and VMs and micro services Vms that have cold boot time and run quickly in a strained environment is looking more like what we will see in the future Yes, especially if you’re using cloud functions V8 is optimized for phones, but Chakra is even more so Looking for opportunities for VMs can be solely optimized for a device target Node take advantage of that VM VM neutrality is an interesting concept VM Vendors trying to optimize it based on workloads of a server Opens opportunities for Node Node Chakra has been proved to iOS. You can cut off jitting off which was a requirement to be able to be in the Apple App Store Node is not just for servers anymore Node doesn’t take a long time configuring it When a developer runs code on an IoT or a mobile app they don’t control the VM that is bundled, they run it on top of Node and it just works. VM neutrality gives a new vector, so you can swam a whole different VM [18:44] When running different engines like iOS vs Android, does the profile change? What it comes down to is if it’s eventive programming The browser is an eventive environment, is very efficient waiting for things to happen before it does something The way that we program servers and nodes are the same as well the basics are the same generally environmental differences exist but the programming model is usually the same What does impact it is memory and processor and hardware and things like that That is where tuning the VM comes into play [20:29] What is the new Async Hooks API used for? Node has been lacking for automated inspection of Async Hook No way for Node to tell you when scheduling and beginning of an Async operation. Hook helps with that it’s a way for developers to write debugging features Node tells the application that it’s working with Asynchronous way. The embedded inspector has been embedded since Node 6 Now has a JavaScript API to use it You can use things like Chrome debugger inside the running node process Old debugging protocol has been removed VM.run is still there but in the process of being deprecated [22:34] How like is the experimental Node API will change? Marked as experimental because it’s the first time in the open Hopefully out of experimental soon Soon can port API to the existing LTS Looking for more people to participate with the new API and give feedback Fix any concerns before it goes to LTS Some other experimental things are in the works like ASync Hooks and how it interacts with promises Renaming some features Another new feature - serializer and deserializer that comes with V8 experimental but will most likely stay [25:31] what is your standard for going to LTS? Major releases every 6 months Next Oct Node 9 will come out and then Node 8 will be LTS Documentation, updates, additions etc will be ready then Plan to do it for 2.5 years Every even releases come out to LTS as the odd release comes out Helps keeps a current line while having something new in the release line Node 6 is the current LTS version [27:26] What are you taking out or deprecating in Node 8? Use the word deprecate sparingly If many people use features, it’s hard to get rid of Security issue with Buffer, constructor argument was ambiguous Had added APIs that were more explicit over time and pushed those Now it will be deprecated [28:43] 21% - 33% Performance increase with some Node updates Someone online updated their React app to Node 8 and found an 21% - 33% increase Benchmarking group tests to make sure things are getting faster V8 is always getting faster as well Code changes fast and so there is a chance performance slows down so they have people to check Benchmark test are all automated by a team [30:47] Is it safe to just switch to Node 8? For front-end, yes clear your NPM cache Back use cases will usually wait until LTS [31:28] Where any of the features hard to implement? The API work took about a year It was a collaboration which made it interesting IBM, Intel, Google were involved The collaboration took a while Also Async hooks took at least a year. Async hooks used to be called async wraps and has been in the work for almost 3 years many of the changes were the accumulation of small chances [33:07] It’s the little things Letting people get small changes in accumulate into a big difference the product gets much better that way [33:57] What versions of Node are you actively updating? Current releases of Node 8 for a half of year Node 6 is LTS Additional year of maintenance of previous LTSs. Schedule is at http://github.com/node8js/lts in a chart Support for Node 4 with only critical updates, Node 6 minor updates, and Node 8 Node 7 doesn’t get much support unless it’s vital security supports. If you’re running 0.10 or 0.12 stop. Those do not get security fixes anymore [35:42] Where do you see things going from here? Mostly still working out Async hooks Maybe add some web worker or worker support for Node JS ES module support Working to make promises better Working on the performance profile and internal systems [20:29] What is the adoption like of Node 8? Node team gets better at getting people to adopt quickly but about 5% - 6% will not upgrade community doubles each year at 8 million users right now Here is a graph on Twitter posted by NPM Limiting breaks and softly deprecating things makes it’s easier to upgrade [40:11] How can people contribute and get involved?  NodeToDo.org shows how to make contribution Occasionally major conferences have information on how to contribute Test it out and help make it stronger [42:08] If people install Node 8 and have issues what can they do? If it’s an NPM problem check with them clear cache! install newest version with: npm install -g npm@latest Report problems to either NPM or Node  If you’re not sure where the problem is, check github.com/nodejs/help  Links Node8 Node’s Twitter Node’s Medium Node Evangelism Group Mikael on Twitter and GitHub Arunesh on Twitter Anna on Twitter PicksAJOverclocked Remix Super Mario RPG Window to The StarsAmiee Blogpost RisingStack on Node 8 2 Frugal Dudes Charles Homeland House of Cards JoeShimmer LakeMikaelBlake2b-wasmAremeshCurrent Nightly NewsSpecial Guests: Anna Henningsen, Arunesh Chandra, and Mikeal Rogers.   Support this podcast at — https://redcircle.com/javascript-jabber/donationsPrivacy &amp; Opt-Out: https://redcircle.com/privacy

JSJ 267 Node 8 with Mikeal Rogers, Arunesh Chandra, and Anna HenningsenOn today’s episode of JavaScript Jabber we have panelists Joe Eames, AJ O’Neil, Amiee Knight and Charles Max Wood and we are talking about Node 8. To help us we have special guests Mikeal Rodgers, Arunesh Chandra, and Anna Henningsen. It’s going to be a great show. Tune in.[1:56] Is Node 8 just an update or is there more?<ul> <li>More than just an update</li> <li>Two main points:</li> <li>Improved <a href="https://www.npmjs.com/package/prana" rel="nofollow" target="_blank">Prana</a> support</li> <li>Native API</li> <li>Native APIs are helpful for Native Add-ons. For both the consumer and the developer side.</li> <li>Prior to update these Node Native modules ran in C++ and bound to specific to Node 8 APIs.</li> <li>Causes these modules to be updated or reconciled every time these modules are rereleased.</li> <li>Creates burden for module maintainers.</li> <li>Creates friction in upgrading Node versions in production departments.</li> <li>If you have a deployment depending on a certain Native module, some of the modules may not get updated in time when updating your Node versions. Keeping people from updating Node.</li> <li>Creates compatibility issues with Node users not using Node 8</li> <li>Experimental support for a Native layer in Node 8 to eliminate these issues as much as possible.</li> <li>Important milestone for the module ecosystem.</li> <li>You can write extensions for Node in C++ and it decouples V8 so you can use something else on the front.</li> <li>Modules takes dependency on V8 API specific to a particular version. So if V8 changes your module will be extracted from that.</li> <li>As a side benefit, you can have another VM to take advantage of that.</li> <li>Major version upgrades mean updating Native modules and usually some of those modules haven’t updated to the newest version of Node and be complicated.</li> <li>Deep dependency wise, about 30% depends on a Native module somewhere</li> <li>In the future, with the Native API, you’ll be able to update Node without breaking modules.</li> </ul>[5:51] What kind of work went into this?<ul> <li>Most of the work was in C++</li> <li>First thing that was done was, they looked at the top dependent Native modules in the ecosystem.</li> <li>Looked for what kind of V8 exposure they had and cataloged it</li> <li>Looked at how these APIs and what their purposes were</li> <li>Looked for a way to extract them so that they are part of Node Core</li> <li>Created neutral APIs, now part of the Node core.</li> <li>All C APIs</li> <li>Also has a C++ wrapper to improves usability of the API.</li> </ul>[7:17] What’s an example of what you can do with these APIs?<ul> <li>Native modules allows for tighter integration and better module performance</li> <li>Specific APIs that you can use in V8 that isn’t available through JavaScript</li> <li>If you have a C++ variable code and you want to expose a variable into JavaScript, that is V8 API note a Node 8 API</li> <li>Having it bound directly to the VM was something they wanted for a long time</li> <li>Google controls V8 and they bind to V8</li> <li>Created a better relationship with Google starting in IOJS</li> <li>Also worked with Microsoft with their Node Shocker work.</li> <li>Same with <a href="https://developer.mozilla.org/en-US/docs/Mozilla/Projects/SpiderMonkey" rel="nofollow" target="_blank">SpiderMonkey</a> </li> <li> <a href="https://github.com/mozilla/spidernode" rel="nofollow" target="_blank">SpiderNode</a> is in the works</li> </ul>[9:23] Have you guys done any testing for performance?<ul> <li>Some. There is a performance working group.</li> <li>There is a need to stay on top of V8</li> <li>V8 team has focused on new language features</li> <li>Many features have been added over the years</li> <li>Many didn’t come in optimized</li> <li>The performance profile has changed with these features</li> <li>If you’re using new language features, you will see a performance boost</li> <li>In core, still tracking down code that was specific to the old optimizer and rewriting i to work the new optimizer</li> <li> <a href="https://turboc.codeplex.com/" rel="nofollow" target="_blank">Turbo C</a> compiler hasn’t landed yet, but is to come.</li> <li>Will have a completely different performance profile</li> <li>In most real world applications it will be faster</li> <li>Waiting on the release to take a version of V8 to make it easier to upgrade features in the future</li> </ul>[11:28] Are the new features picked up from V8 or implemented in Node?<ul> <li>It’s all in V8</li> <li>Better longterm support</li> <li>Promises are made better in Node as a platform</li> <li>Added new method called util.promisify()</li> <li>Implementation comes from V8</li> <li>Allows for more optimization for promises in Node core</li> <li>Promise support for the one-deprecated domains module.</li> </ul>[13:02] Is there anything more than NMP 5?<ul> <li>First off, delete your NMP cache.</li> <li>It’s in your home directory usually with a .npm extension</li> </ul>[14:09] What are the new features in V8?<ul><li>Unlimited heap sizes, previously had a 4gb limit. No fixed limit.</li></ul>[14:09] Will you see things like chakra come out tuned for servers?<ul> <li>Profiles of a server for application process are getting smaller</li> <li>Getting cut into containers and VMs and micro services</li> <li>Vms that have cold boot time and run quickly in a strained environment is looking more like what we will see in the future</li> <li>Yes, especially if you’re using cloud functions</li> <li>V8 is optimized for phones, but Chakra is even more so</li> <li>Looking for opportunities for VMs can be solely optimized for a device target</li> <li>Node take advantage of that VM</li> <li>VM neutrality is an interesting concept</li> <li>VM Vendors trying to optimize it based on workloads of a server</li> <li>Opens opportunities for Node</li> <li>Node Chakra has been proved to iOS. You can cut off jitting off which was a requirement to be able to be in the Apple App Store</li> <li>Node is not just for servers anymore</li> <li>Node doesn’t take a long time configuring it</li> <li>When a developer runs code on an IoT or a mobile app they don’t control the VM that is bundled, they run it on top of Node and it just works.</li> <li>VM neutrality gives a new vector, so you can swam a whole different VM</li> </ul>[18:44] When running different engines like iOS vs Android, does the profile change?<ul> <li>What it comes down to is if it’s eventive programming</li> <li>The browser is an eventive environment, is very efficient waiting for things to happen before it does something</li> <li>The way that we program servers and nodes are the same as well</li> <li>the basics are the same generally</li> <li>environmental differences exist but the programming model is usually the same</li> <li>What does impact it is memory and processor and hardware and things like that</li> <li>That is where tuning the VM comes into play</li> </ul>[20:29] What is the new Async Hooks API used for?<ul> <li>Node has been lacking for automated inspection of Async Hook</li> <li>No way for Node to tell you when scheduling and beginning of an Async operation. Hook helps with that</li> <li>it’s a way for developers to write debugging features</li> <li>Node tells the application that it’s working with Asynchronous way.</li> <li>The embedded inspector has been embedded since Node 6</li> <li>Now has a JavaScript API to use it</li> <li>You can use things like Chrome debugger inside the running node process</li> <li>Old debugging protocol has been removed</li> <li>VM.run is still there but in the process of being deprecated</li> </ul>[22:34] How like is the experimental Node API will change?<ul> <li>Marked as experimental because it’s the first time in the open</li> <li>Hopefully out of experimental soon</li> <li>Soon can port API to the existing LTS</li> <li>Looking for more people to participate with the new API and give feedback</li> <li>Fix any concerns before it goes to LTS</li> <li>Some other experimental things are in the works like ASync Hooks and how it interacts with promises</li> <li>Renaming some features</li> <li>Another new feature - serializer and deserializer that comes with V8</li> <li>experimental but will most likely stay</li> </ul>[25:31] what is your standard for going to LTS?<ul> <li>Major releases every 6 months</li> <li>Next Oct Node 9 will come out and then Node 8 will be LTS</li> <li>Documentation, updates, additions etc will be ready then</li> <li>Plan to do it for 2.5 years</li> <li>Every even releases come out to LTS as the odd release comes out</li> <li>Helps keeps a current line while having something new in the release line</li> <li>Node 6 is the current LTS version</li> </ul>[27:26] What are you taking out or deprecating in Node 8?<ul> <li>Use the word deprecate sparingly</li> <li>If many people use features, it’s hard to get rid of</li> <li>Security issue with Buffer, constructor argument was ambiguous</li> <li>Had added APIs that were more explicit over time and pushed those</li> <li>Now it will be deprecated</li> </ul>[28:43] 21% - 33% Performance increase with some Node updates<ul> <li>Someone online updated their React app to Node 8 and found an 21% - 33% increase</li> <li>Benchmarking group tests to make sure things are getting faster</li> <li>V8 is always getting faster as well</li> <li>Code changes fast and so there is a chance performance slows down so they have people to check</li> <li>Benchmark test are all automated by a team</li> </ul>[30:47] Is it safe to just switch to Node 8?<ul> <li>For front-end, yes</li> <li>clear your NPM cache</li> <li>Back use cases will usually wait until LTS</li> </ul>[31:28] Where any of the features hard to implement?<ul> <li>The API work took about a year</li> <li>It was a collaboration which made it interesting</li> <li>IBM, Intel, Google were involved</li> <li>The collaboration took a while</li> <li>Also Async hooks took at least a year.</li> <li>Async hooks used to be called async wraps and has been in the work for almost 3 years</li> <li>many of the changes were the accumulation of small chances</li> </ul>[33:07] It’s the little things<ul> <li>Letting people get small changes in accumulate into a big difference</li> <li>the product gets much better that way</li> </ul>[33:57] What versions of Node are you actively updating?<ul> <li>Current releases of Node 8 for a half of year</li> <li>Node 6 is LTS</li> <li>Additional year of maintenance of previous LTSs.</li> <li>Schedule is at <a href="http://github.com/node8js/lts" rel="nofollow" target="_blank">http://github.com/node8js/lts</a> in a chart</li> <li>Support for Node 4 with only critical updates, Node 6 minor updates, and Node 8</li> <li>Node 7 doesn’t get much support unless it’s vital security supports.</li> <li>If you’re running 0.10 or 0.12 stop. Those do not get security fixes anymore</li> </ul>[35:42] Where do you see things going from here?<ul> <li>Mostly still working out Async hooks</li> <li>Maybe add some web worker or worker support for Node JS</li> <li>ES module support</li> <li>Working to make promises better</li> <li>Working on the performance profile and internal systems</li> </ul>[20:29] What is the adoption like of Node 8?<ul> <li>Node team gets better at getting people to adopt quickly</li> <li>but about 5% - 6% will not upgrade</li> <li>community doubles each year at 8 million users right now</li> <li><a href="https://hackernoon.com/upgrading-from-node-6-to-node-8-a-real-world-performance-comparison-3dfe1fbc92a3" rel="nofollow" target="_blank">Here is a graph on Twitter posted by NPM</a></li> <li>Limiting breaks and softly deprecating things makes it’s easier to upgrade</li> </ul>[40:11] How can people contribute and get involved?<ul> <li> <a href="http://nodetodo.org" rel="nofollow" target="_blank">NodeToDo.org</a> shows how to make contribution</li> <li>Occasionally major conferences have information on how to contribute</li> <li>Test it out and help make it stronger</li> </ul>[42:08] If people install Node 8 and have issues what can they do?<ul> <li>If it’s an NPM problem check with them</li> <li>clear cache!</li> <li>install newest version with: npm install -g npm@latest</li> <li>Report problems to either <a href="http://github.com/nmp/nmp" rel="nofollow" target="_blank">NPM</a> or <a href="http://github.com/nodejs/node" rel="nofollow" target="_blank">Node</a> </li> <li>If you’re not sure where the problem is, check <a href="http://github.com/nodejs/help" rel="nofollow" target="_blank">github.com/nodejs/help</a> </li> </ul>Links <a href="https://nodejs.org/en/blog/release/v8.0.0/" rel="nofollow" target="_blank">Node8</a> <a href="https://twitter.com/nodejs" rel="nofollow" target="_blank">Node’s Twitter</a> <a href="https://medium.com/@nodejs" rel="nofollow" target="_blank">Node’s Medium</a> <a href="http://github.com/nodejs/evangelism/" rel="nofollow" target="_blank">Node Evangelism Group</a> Mikael on <a href="https://twitter.com/mikeal" rel="nofollow" target="_blank">Twitter</a> and <a href="https://github.com/mikeal" rel="nofollow" target="_blank">GitHub</a> Arunesh on <a href="https://twitter.com/AruneshC" rel="nofollow" target="_blank">Twitter</a> Anna on <a href="https://twitter.com/addaleax" rel="nofollow" target="_blank">Twitter</a> PicksAJ<a href="http://smrpg.ocremix.org/" rel="nofollow" target="_blank">Overclocked Remix Super Mario RPG Window to The Stars</a>Amiee <a href="https://blog.risingstack.com/important-features-fixes-node-js-version-8/" rel="nofollow" target="_blank">Blogpost RisingStack on Node 8</a><br/> <a href="http://2frugaldudes.com/" rel="nofollow" target="_blank">2 Frugal Dudes</a> Charles <a href="http://www.sho.com/homeland" rel="nofollow" target="_blank">Homeland</a><br/> <a href="http://house-of-cards.wikia.com/wiki/Main_Page" rel="nofollow" target="_blank">House of Cards</a> Joe<a href="https://www.youtube.com/watch?v=sm_hwxNTAa0" rel="nofollow" target="_blank">Shimmer Lake</a>Mikael<a href="https://github.com/mafintosh/blake2b-wasm" rel="nofollow" target="_blank">Blake2b-wasm</a>AremeshCurrent Nightly NewsSpecial Guests: Anna Henningsen, Arunesh Chandra, and Mikeal Rogers.   <br/><br/>Support this podcast at — <a href="https://redcircle.com/javascript-jabber/donations" rel="payment nofollow" target="_blank">https://redcircle.com/javascript-jabber/donations</a><br/><br/>Privacy &amp; Opt-Out: <a href="https://redcircle.com/privacy" rel="nofollow" target="_blank">https://redcircle.com/privacy</a>

JSJ 267 Node 8 with Mikeal Rogers, Arunesh Chandra, and Anna Henningsen

JSJ 267 Node 8 with Mikeal Rogers, Arunesh Chandra, and Anna HenningsenOn today’s episode of JavaScript Jabber we have panelists Joe Eames, AJ O’Neil, Amiee Knight and Charles Max Wood and we are talking about Node 8. To help us we have special guests Mikeal Rodgers, Arunesh Chandra, and Anna Henningsen. It’s going to be a great show. Tune in.[1:56] Is Node 8 just an update or is there more? More than just an update Two main points: Improved Prana support Native API Native APIs are helpful for Native Add-ons. For both the consumer and the developer side. Prior to update these Node Native modules ran in C++ and bound to specific to Node 8 APIs. Causes these modules to be updated or reconciled every time these modules are rereleased. Creates burden for module maintainers. Creates friction in upgrading Node versions in production departments. If you have a deployment depending on a certain Native module, some of the modules may not get updated in time when updating your Node versions. Keeping people from updating Node. Creates compatibility issues with Node users not using Node 8 Experimental support for a Native layer in Node 8 to eliminate these issues as much as possible. Important milestone for the module ecosystem. You can write extensions for Node in C++ and it decouples V8 so you can use something else on the front. Modules takes dependency on V8 API specific to a particular version. So if V8 changes your module will be extracted from that. As a side benefit, you can have another VM to take advantage of that. Major version upgrades mean updating Native modules and usually some of those modules haven’t updated to the newest version of Node and be complicated. Deep dependency wise, about 30% depends on a Native module somewhere In the future, with the Native API, you’ll be able to update Node without breaking modules. [5:51] What kind of work went into this? Most of the work was in C++ First thing that was done was, they looked at the top dependent Native modules in the ecosystem. Looked for what kind of V8 exposure they had and cataloged it Looked at how these APIs and what their purposes were Looked for a way to extract them so that they are part of Node Core Created neutral APIs, now part of the Node core. All C APIs Also has a C++ wrapper to improves usability of the API. [7:17] What’s an example of what you can do with these APIs? Native modules allows for tighter integration and better module performance Specific APIs that you can use in V8 that isn’t available through JavaScript If you have a C++ variable code and you want to expose a variable into JavaScript, that is V8 API note a Node 8 API Having it bound directly to the VM was something they wanted for a long time Google controls V8 and they bind to V8 Created a better relationship with Google starting in IOJS Also worked with Microsoft with their Node Shocker work. Same with SpiderMonkey SpiderNode is in the works [9:23] Have you guys done any testing for performance? Some. There is a performance working group. There is a need to stay on top of V8 V8 team has focused on new language features Many features have been added over the years Many didn’t come in optimized The performance profile has changed with these features If you’re using new language features, you will see a performance boost In core, still tracking down code that was specific to the old optimizer and rewriting i to work the new optimizer Turbo C compiler hasn’t landed yet, but is to come. Will have a completely different performance profile In most real world applications it will be faster Waiting on the release to take a version of V8 to make it easier to upgrade features in the future [11:28] Are the new features picked up from V8 or implemented in Node? It’s all in V8 Better longterm support Promises are made better in Node as a platform Added new method called util.promisify() Implementation comes from V8 Allows for more optimization for promises in Node core Promise support for the one-deprecated domains module. [13:02] Is there anything more than NMP 5? First off, delete your NMP cache. It’s in your home directory usually with a .npm extension [14:09] What are the new features in V8? Unlimited heap sizes, previously had a 4gb limit. No fixed limit. [14:09] Will you see things like chakra come out tuned for servers? Profiles of a server for application process are getting smaller Getting cut into containers and VMs and micro services Vms that have cold boot time and run quickly in a strained environment is looking more like what we will see in the future Yes, especially if you’re using cloud functions V8 is optimized for phones, but Chakra is even more so Looking for opportunities for VMs can be solely optimized for a device target Node take advantage of that VM VM neutrality is an interesting concept VM Vendors trying to optimize it based on workloads of a server Opens opportunities for Node Node Chakra has been proved to iOS. You can cut off jitting off which was a requirement to be able to be in the Apple App Store Node is not just for servers anymore Node doesn’t take a long time configuring it When a developer runs code on an IoT or a mobile app they don’t control the VM that is bundled, they run it on top of Node and it just works. VM neutrality gives a new vector, so you can swam a whole different VM [18:44] When running different engines like iOS vs Android, does the profile change? What it comes down to is if it’s eventive programming The browser is an eventive environment, is very efficient waiting for things to happen before it does something The way that we program servers and nodes are the same as well the basics are the same generally environmental differences exist but the programming model is usually the same What does impact it is memory and processor and hardware and things like that That is where tuning the VM comes into play [20:29] What is the new Async Hooks API used for? Node has been lacking for automated inspection of Async Hook No way for Node to tell you when scheduling and beginning of an Async operation. Hook helps with that it’s a way for developers to write debugging features Node tells the application that it’s working with Asynchronous way. The embedded inspector has been embedded since Node 6 Now has a JavaScript API to use it You can use things like Chrome debugger inside the running node process Old debugging protocol has been removed VM.run is still there but in the process of being deprecated [22:34] How like is the experimental Node API will change? Marked as experimental because it’s the first time in the open Hopefully out of experimental soon Soon can port API to the existing LTS Looking for more people to participate with the new API and give feedback Fix any concerns before it goes to LTS Some other experimental things are in the works like ASync Hooks and how it interacts with promises Renaming some features Another new feature - serializer and deserializer that comes with V8 experimental but will most likely stay [25:31] what is your standard for going to LTS? Major releases every 6 months Next Oct Node 9 will come out and then Node 8 will be LTS Documentation, updates, additions etc will be ready then Plan to do it for 2.5 years Every even releases come out to LTS as the odd release comes out Helps keeps a current line while having something new in the release line Node 6 is the current LTS version [27:26] What are you taking out or deprecating in Node 8? Use the word deprecate sparingly If many people use features, it’s hard to get rid of Security issue with Buffer, constructor argument was ambiguous Had added APIs that were more explicit over time and pushed those Now it will be deprecated [28:43] 21% - 33% Performance increase with some Node updates Someone online updated their React app to Node 8 and found an 21% - 33% increase Benchmarking group tests to make sure things are getting faster V8 is always getting faster as well Code changes fast and so there is a chance performance slows down so they have people to check Benchmark test are all automated by a team [30:47] Is it safe to just switch to Node 8? For front-end, yes clear your NPM cache Back use cases will usually wait until LTS [31:28] Where any of the features hard to implement? The API work took about a year It was a collaboration which made it interesting IBM, Intel, Google were involved The collaboration took a while Also Async hooks took at least a year. Async hooks used to be called async wraps and has been in the work for almost 3 years many of the changes were the accumulation of small chances [33:07] It’s the little things Letting people get small changes in accumulate into a big difference the product gets much better that way [33:57] What versions of Node are you actively updating? Current releases of Node 8 for a half of year Node 6 is LTS Additional year of maintenance of previous LTSs. Schedule is at http://github.com/node8js/lts in a chart Support for Node 4 with only critical updates, Node 6 minor updates, and Node 8 Node 7 doesn’t get much support unless it’s vital security supports. If you’re running 0.10 or 0.12 stop. Those do not get security fixes anymore [35:42] Where do you see things going from here? Mostly still working out Async hooks Maybe add some web worker or worker support for Node JS ES module support Working to make promises better Working on the performance profile and internal systems [20:29] What is the adoption like of Node 8? Node team gets better at getting people to adopt quickly but about 5% - 6% will not upgrade community doubles each year at 8 million users right now Here is a graph on Twitter posted by NPM Limiting breaks and softly deprecating things makes it’s easier to upgrade [40:11] How can people contribute and get involved? NodeToDo.org shows how to make contribution Occasionally major conferences have information on how to contribute Test it out and help make it stronger [42:08] If people install Node 8 and have issues what can they do? If it’s an NPM problem check with them clear cache! install newest version with: npm install -g npm@latest Report problems to either NPM or Node If you’re not sure where the problem is, check github.com/nodejs/help LinksNode8 Node’s Twitter Node’s Medium Node Evangelism GroupMikael on Twitter and GitHub Arunesh on Twitter Anna on TwitterPicksAJOverclocked Remix Super Mario RPG Window to The StarsAmieeBlogpost RisingStack on Node 8 2 Frugal DudesCharlesHomeland House of CardsJoeShimmer LakeMikaelBlake2b-wasmAremeshCurrent Nightly News

<h4>JSJ 267 Node 8 with Mikeal Rogers, Arunesh Chandra, and Anna Henningsen</h4><p>On today’s episode of JavaScript Jabber we have panelists Joe Eames, AJ O’Neil, Amiee Knight and Charles Max Wood and we are talking about Node 8. To help us we have special guests Mikeal Rodgers, Arunesh Chandra, and Anna Henningsen. It’s going to be a great show. Tune in.</p><h5>[1:56] Is Node 8 just an update or is there more?</h5><ul> <li>More than just an update</li> <li>Two main points:</li> <li>Improved <a href="https://www.npmjs.com/package/prana" rel="nofollow" target="_blank">Prana</a> support</li> <li>Native API</li> <li>Native APIs are helpful for Native Add-ons. For both the consumer and the developer side.</li> <li>Prior to update these Node Native modules ran in C++ and bound to specific to Node 8 APIs.</li> <li>Causes these modules to be updated or reconciled every time these modules are rereleased.</li> <li>Creates burden for module maintainers.</li> <li>Creates friction in upgrading Node versions in production departments.</li> <li>If you have a deployment depending on a certain Native module, some of the modules may not get updated in time when updating your Node versions. Keeping people from updating Node.</li> <li>Creates compatibility issues with Node users not using Node 8</li> <li>Experimental support for a Native layer in Node 8 to eliminate these issues as much as possible.</li> <li>Important milestone for the module ecosystem.</li> <li>You can write extensions for Node in C++ and it decouples V8 so you can use something else on the front.</li> <li>Modules takes dependency on V8 API specific to a particular version. So if V8 changes your module will be extracted from that.</li> <li>As a side benefit, you can have another VM to take advantage of that.</li> <li>Major version upgrades mean updating Native modules and usually some of those modules haven’t updated to the newest version of Node and be complicated.</li> <li>Deep dependency wise, about 30% depends on a Native module somewhere</li> <li>In the future, with the Native API, you’ll be able to update Node without breaking modules.</li> </ul><h5>[5:51] What kind of work went into this?</h5><ul> <li>Most of the work was in C++</li> <li>First thing that was done was, they looked at the top dependent Native modules in the ecosystem.</li> <li>Looked for what kind of V8 exposure they had and cataloged it</li> <li>Looked at how these APIs and what their purposes were</li> <li>Looked for a way to extract them so that they are part of Node Core</li> <li>Created neutral APIs, now part of the Node core.</li> <li>All C APIs</li> <li>Also has a C++ wrapper to improves usability of the API.</li> </ul><h5>[7:17] What’s an example of what you can do with these APIs?</h5><ul> <li>Native modules allows for tighter integration and better module performance</li> <li>Specific APIs that you can use in V8 that isn’t available through JavaScript</li> <li>If you have a C++ variable code and you want to expose a variable into JavaScript, that is V8 API note a Node 8 API</li> <li>Having it bound directly to the VM was something they wanted for a long time</li> <li>Google controls V8 and they bind to V8</li> <li>Created a better relationship with Google starting in IOJS</li> <li>Also worked with Microsoft with their Node Shocker work.</li> <li>Same with <a href="https://developer.mozilla.org/en-US/docs/Mozilla/Projects/SpiderMonkey" rel="nofollow" target="_blank">SpiderMonkey</a></li> <li><a href="https://github.com/mozilla/spidernode" rel="nofollow" target="_blank">SpiderNode</a> is in the works</li> </ul><h5>[9:23] Have you guys done any testing for performance?</h5><ul> <li>Some. There is a performance working group.</li> <li>There is a need to stay on top of V8</li> <li>V8 team has focused on new language features</li> <li>Many features have been added over the years</li> <li>Many didn’t come in optimized</li> <li>The performance profile has changed with these features</li> <li>If you’re using new language features, you will see a performance boost</li> <li>In core, still tracking down code that was specific to the old optimizer and rewriting i to work the new optimizer</li> <li><a href="https://turboc.codeplex.com/" rel="nofollow" target="_blank">Turbo C</a> compiler hasn’t landed yet, but is to come.</li> <li>Will have a completely different performance profile</li> <li>In most real world applications it will be faster</li> <li>Waiting on the release to take a version of V8 to make it easier to upgrade features in the future</li> </ul><h5>[11:28] Are the new features picked up from V8 or implemented in Node?</h5><ul> <li>It’s all in V8</li> <li>Better longterm support</li> <li>Promises are made better in Node as a platform</li> <li>Added new method called <code>util.promisify()</code></li> <li>Implementation comes from V8</li> <li>Allows for more optimization for promises in Node core</li> <li>Promise support for the one-deprecated domains module.</li> </ul><h5>[13:02] Is there anything more than NMP 5?</h5><ul> <li>First off, delete your NMP cache.</li> <li>It’s in your home directory usually with a .npm extension</li> </ul><h5>[14:09] What are the new features in V8?</h5><ul> <li>Unlimited heap sizes, previously had a 4gb limit. No fixed limit.</li> </ul><h5>[14:09] Will you see things like chakra come out tuned for servers?</h5><ul> <li>Profiles of a server for application process are getting smaller</li> <li>Getting cut into containers and VMs and micro services</li> <li>Vms that have cold boot time and run quickly in a strained environment is looking more like what we will see in the future</li> <li>Yes, especially if you’re using cloud functions</li> <li>V8 is optimized for phones, but Chakra is even more so</li> <li>Looking for opportunities for VMs can be solely optimized for a device target</li> <li>Node take advantage of that VM</li> <li>VM neutrality is an interesting concept</li> <li>VM Vendors trying to optimize it based on workloads of a server</li> <li>Opens opportunities for Node</li> <li>Node Chakra has been proved to iOS. You can cut off jitting off which was a requirement to be able to be in the Apple App Store</li> <li>Node is not just for servers anymore</li> <li>Node doesn’t take a long time configuring it</li> <li>When a developer runs code on an IoT or a mobile app they don’t control the VM that is bundled, they run it on top of Node and it just works.</li> <li>VM neutrality gives a new vector, so you can swam a whole different VM</li> </ul><h5>[18:44] When running different engines like iOS vs Android, does the profile change?</h5><ul> <li>What it comes down to is if it’s eventive programming</li> <li>The browser is an eventive environment, is very efficient waiting for things to happen before it does something</li> <li>The way that we program servers and nodes are the same as well</li> <li>the basics are the same generally</li> <li>environmental differences exist but the programming model is usually the same</li> <li>What does impact it is memory and processor and hardware and things like that</li> <li>That is where tuning the VM comes into play</li> </ul><h5>[20:29] What is the new Async Hooks API used for?</h5><ul> <li>Node has been lacking for automated inspection of Async Hook</li> <li>No way for Node to tell you when scheduling and beginning of an Async operation. Hook helps with that</li> <li>it’s a way for developers to write debugging features</li> <li>Node tells the application that it’s working with Asynchronous way.</li> <li>The embedded inspector has been embedded since Node 6</li> <li>Now has a JavaScript API to use it</li> <li>You can use things like Chrome debugger inside the running node process</li> <li>Old debugging protocol has been removed</li> <li>VM.run is still there but in the process of being deprecated</li> </ul><h5>[22:34] How like is the experimental Node API will change?</h5><ul> <li>Marked as experimental because it’s the first time in the open</li> <li>Hopefully out of experimental soon</li> <li>Soon can port API to the existing LTS</li> <li>Looking for more people to participate with the new API and give feedback</li> <li>Fix any concerns before it goes to LTS</li> <li>Some other experimental things are in the works like ASync Hooks and how it interacts with promises</li> <li>Renaming some features</li> <li>Another new feature - serializer and deserializer that comes with V8</li> <li>experimental but will most likely stay</li> </ul><h5>[25:31] what is your standard for going to LTS?</h5><ul> <li>Major releases every 6 months</li> <li>Next Oct Node 9 will come out and then Node 8 will be LTS</li> <li>Documentation, updates, additions etc will be ready then</li> <li>Plan to do it for 2.5 years</li> <li>Every even releases come out to LTS as the odd release comes out</li> <li>Helps keeps a current line while having something new in the release line</li> <li>Node 6 is the current LTS version</li> </ul><h5>[27:26] What are you taking out or deprecating in Node 8?</h5><ul> <li>Use the word deprecate sparingly</li> <li>If many people use features, it’s hard to get rid of</li> <li>Security issue with Buffer, constructor argument was ambiguous</li> <li>Had added APIs that were more explicit over time and pushed those</li> <li>Now it will be deprecated</li> </ul><h5>[28:43] 21% - 33% Performance increase with some Node updates</h5><ul> <li>Someone online updated their React app to Node 8 and found an 21% - 33% increase</li> <li>Benchmarking group tests to make sure things are getting faster</li> <li>V8 is always getting faster as well</li> <li>Code changes fast and so there is a chance performance slows down so they have people to check</li> <li>Benchmark test are all automated by a team</li> </ul><h5>[30:47] Is it safe to just switch to Node 8?</h5><ul> <li>For front-end, yes</li> <li>clear your NPM cache</li> <li>Back use cases will usually wait until LTS</li> </ul><h5>[31:28] Where any of the features hard to implement?</h5><ul> <li>The API work took about a year</li> <li>It was a collaboration which made it interesting</li> <li>IBM, Intel, Google were involved</li> <li>The collaboration took a while</li> <li>Also Async hooks took at least a year.</li> <li>Async hooks used to be called async wraps and has been in the work for almost 3 years</li> <li>many of the changes were the accumulation of small chances</li> </ul><h5>[33:07] It’s the little things</h5><ul> <li>Letting people get small changes in accumulate into a big difference</li> <li>the product gets much better that way</li> </ul><h5>[33:57] What versions of Node are you actively updating?</h5><ul> <li>Current releases of Node 8 for a half of year</li> <li>Node 6 is LTS</li> <li>Additional year of maintenance of previous LTSs.</li> <li>Schedule is at <a href="http://github.com/node8js/lts" rel="nofollow" target="_blank">http://github.com/node8js/lts</a> in a chart</li> <li>Support for Node 4 with only critical updates, Node 6 minor updates, and Node 8</li> <li>Node 7 doesn’t get much support unless it’s vital security supports.</li> <li>If you’re running 0.10 or 0.12 stop. Those do not get security fixes anymore</li> </ul><h5>[35:42] Where do you see things going from here?</h5><ul> <li>Mostly still working out Async hooks</li> <li>Maybe add some web worker or worker support for Node JS</li> <li>ES module support</li> <li>Working to make promises better</li> <li>Working on the performance profile and internal systems</li> </ul><h5>[20:29] What is the adoption like of Node 8?</h5><ul> <li>Node team gets better at getting people to adopt quickly</li> <li>but about 5% - 6% will not upgrade</li> <li>community doubles each year at 8 million users right now</li> <li><a href="https://hackernoon.com/upgrading-from-node-6-to-node-8-a-real-world-performance-comparison-3dfe1fbc92a3" rel="nofollow" target="_blank">Here is a graph on Twitter posted by NPM</a></li> <li>Limiting breaks and softly deprecating things makes it’s easier to upgrade</li> </ul><h5>[40:11] How can people contribute and get involved?</h5><ul> <li><a href="http://nodetodo.org" rel="nofollow" target="_blank">NodeToDo.org</a> shows how to make contribution</li> <li>Occasionally major conferences have information on how to contribute</li> <li>Test it out and help make it stronger</li> </ul><h5>[42:08] If people install Node 8 and have issues what can they do?</h5><ul> <li>If it’s an NPM problem check with them</li> <li>clear cache!</li> <li>install newest version with: <code>npm install -g npm@latest</code></li> <li>Report problems to either <a href="http://github.com/nmp/nmp" rel="nofollow" target="_blank">NPM</a> or <a href="http://github.com/nodejs/node" rel="nofollow" target="_blank">Node</a></li> <li>If you’re not sure where the problem is, check <a href="http://github.com/nodejs/help" rel="nofollow" target="_blank">github.com/nodejs/help</a></li> </ul><h4>Links</h4><p><a href="https://nodejs.org/en/blog/release/v8.0.0/" rel="nofollow" target="_blank">Node8</a> <a href="https://twitter.com/nodejs" rel="nofollow" target="_blank">Node’s Twitter</a> <a href="https://medium.com/@nodejs" rel="nofollow" target="_blank">Node’s Medium</a> <a href="http://github.com/nodejs/evangelism/" rel="nofollow" target="_blank">Node Evangelism Group</a></p><p>Mikael on <a href="https://twitter.com/mikeal" rel="nofollow" target="_blank">Twitter</a> and <a href="https://github.com/mikeal" rel="nofollow" target="_blank">GitHub</a> Arunesh on <a href="https://twitter.com/AruneshC" rel="nofollow" target="_blank">Twitter</a> Anna on <a href="https://twitter.com/addaleax" rel="nofollow" target="_blank">Twitter</a></p><h4>Picks</h4><h5>AJ</h5><p><a href="http://smrpg.ocremix.org/" rel="nofollow" target="_blank">Overclocked Remix Super Mario RPG Window to The Stars</a></p><h5>Amiee</h5><p><a href="https://blog.risingstack.com/important-features-fixes-node-js-version-8/" rel="nofollow" target="_blank">Blogpost RisingStack on Node 8</a><br/> <a href="http://2frugaldudes.com/" rel="nofollow" target="_blank">2 Frugal Dudes</a></p><h5>Charles</h5><p><a href="http://www.sho.com/homeland" rel="nofollow" target="_blank">Homeland</a><br/> <a href="http://house-of-cards.wikia.com/wiki/Main_Page" rel="nofollow" target="_blank">House of Cards</a></p><h5>Joe</h5><p><a href="https://www.youtube.com/watch?v=sm_hwxNTAa0" rel="nofollow" target="_blank">Shimmer Lake</a></p><h5>Mikael</h5><p><a href="https://github.com/mafintosh/blake2b-wasm" rel="nofollow" target="_blank">Blake2b-wasm</a></p><h5>Aremesh</h5><p>Current Nightly News</p>