V8, Advanced JavaScript, and the Next Performance Frontier [video]
1–10 of 47 posts
Re: V8, Advanced JavaScript, and the Next Performance Frontier [video]
#2It was cool seeing a demo at the end made using Choo[1]. Choo is my favorite in the current sea of react clones. I like it because its tiny (4k vs react's ~200k). Choo supports server-side rendering. And its made out of smaller modules which are all independently useful (DOM generator, diff engine and router).
Instead of using JSX files, choo uses ES6 tagged template literals. As a result the code doesn't need a compilation step at all. But you can still actually compile the templates if you want for better performance + a smaller JS bundle in production.
Its great stuff. I'm a huge fan.
Re: V8, Advanced JavaScript, and the Next Performance Frontier [video]
#3Demo showing how to debug node code using Chrome DevTools at 26:18[1]. Very cool if you don't already have a full blown IDE with debugging built in. Or even if you just want to inspect some random node library/code on the fly.
Re: V8, Advanced JavaScript, and the Next Performance Frontier [video]
#4Demo showing how to debug node code using Chrome DevTools at 26:18[1]. Very cool if you don't already have a full blown IDE with debugging built in. Or even if you just want to inspect some random node library/code on the fly. 1. https://youtu.be/EdFDJANJJLs?t=26m18s
Have you by chance found how to do that with babel-node?
It seems that after introducing a built-in chrome protocol debugger node-inspector was abandoned and now I can't figure out how to use the built-in debugger with babel-node.
Re: V8, Advanced JavaScript, and the Next Performance Frontier [video]
#5It was cool seeing a demo at the end made using Choo[1]. Choo is my favorite in the current sea of react clones. I like it because its tiny (4k vs react's ~200k). Choo supports server-side rendering. And its made out of smaller modules which are all independently useful (DOM generator, diff engine and router). Instead of using JSX files, choo uses ES6 tagged template literals. As a result the code doesn't need a comp…
performance isn't great, though: https://rawgit.com/krausest/js-framework-benchmark/master/we...
Re: V8, Advanced JavaScript, and the Next Performance Frontier [video]
#6Does this make babel obsolete on the server side?
Re: V8, Advanced JavaScript, and the Next Performance Frontier [video]
#7Does this make babel obsolete on the server side?
You don't have to use Babel, but if you want to use newer/syntax not in Node/v8 then yes. Always a tradeoff, but gave a talk at TC39 recently about this, https://github.com/hzoo/role-of-babel-in-js, https://twitter.com/left_pad/status/867593358977499137.
https://github.com/babel/babel-preset-env with our `"node": "current"` option can help with this.
Re: V8, Advanced JavaScript, and the Next Performance Frontier [video]
#8Demo showing how to debug node code using Chrome DevTools at 26:18[1]. Very cool if you don't already have a full blown IDE with debugging built in. Or even if you just want to inspect some random node library/code on the fly. 1. https://youtu.be/EdFDJANJJLs?t=26m18s
Have you by chance found how to do that with babel-node? It seems that after introducing a built-in chrome protocol debugger node-inspector was abandoned and now I can't figure out how to use the built-in debugger with babel-node.
I just tested and it looks like `babel-node --inspect` works fine. However `--inspect-brk` does require this small PR: https://github.com/babel/babel/pull/5785
And FWIW, my written guide here captures the basics that Seth covered in the video: https://medium.com/@paul_irish/debugging-node-js-nightlies-w...
Re: V8, Advanced JavaScript, and the Next Performance Frontier [video]
#9TL;DW?
Re: V8, Advanced JavaScript, and the Next Performance Frontier [video]
#10TL;DW?
Basically Ignition + TurboFan:
https://v8project.blogspot.com/2017/05/launching-ignition-an...
with a (really) brief mention of Orinoco:
https://v8project.blogspot.com/2016/04/jank-busters-part-two...
and Node + Chrome DevTools:
https://medium.com/@paul_irish/debugging-node-js-nightlies-w...
Octane benchmark retired because it benchmarks peak performance and doesn't account for other factors (e.g. startup time, memory usage). Speedometer2 coming to browserbench.org soon, benchmarks a much wider range of real-world frameworks.