Franziska Hinkelmann is a compiler engineer on the v8 team at Google. This is a live blog. Doing the best I can to keep up and be accurate. Thanks for your understanding. — Tom
"What is node? It's AWESOME. That's the only joke you'll get in this 20 minutes."
It provides asynchronous I/O, based on event loops.
100,000 lines of JS and C++ code, gluing v8 to server-side I/O and implementing Node modules.
And of course it is an ecosystem of open source packages (npm).
Includes a just-in-time compiler (converts to very fast code on the fly) and performs speculative optimizations.
v8 is written in C++ and implements the EcmaScript specification.
What v8 isn't:
It's not the I/O — it's not access to the filesystem. Those things are provided by libuv and Node.js itself.
It's not the DOM — that's provided by browsers themselves.
No v8 commit can land if it breaks node.
Porting native add-ons [think of the mongodb driver that is slightly faster if it can use C++] is a challenge for Node on different VMs. The new N-API makes it easy to use different engines.