As mentioned earlier, we are planning to ship the new compiler architecture based on the Ignition interpreter and the TurboFan compiler this year, ideally by the end of this quarter. Despite holidays we have made a lot of progress with getting closer to the finish line. For example we have finally caught up with the default configuration (based on fullcodegen and Crankshaft) on the AcmeAir benchmark used to measure Node.js throughput performance.

I'm also excited about the page load time improvements we achieved with Ignition and TurboFan on various pages, as this area is highly relevant to the web performance crisis.

Most of these improvements are possible because we can reduce the number of optimizations and deoptimizations during startup, but also because we need to parse only once now to generate Ignition bytecode, and optimized code is then generated from bytecode rather than having to reparse the function for Crankshaft.

In 2017 the V8 team wants to engage more actively with the JavaScript community, both the world wide community, but also the local community in the Munich area. I just gave a talk on High-Speed ES2015 at this months' Munich Node.js User Group meetup, and we will speak about benchmarks and real world performance at the next MunichJS User Group meetup. I'm excited to announce that we will host both the next MunichJS User Group meetup in February and the next Munich Node User Group meetup in March in our new Isar Valley event space at Google Munich - with Pizza and gBräu!

Of course we also submitted a lot of talk proposals to various JavaScript and Node conferences, so expect to meet a lot more V8 folks, especially folks that you may not know in person yet, this year (depending on acceptance of these proposals, of course).