
@GoogleChrome / @v8js / Blink • Opinions are mine
48.142869, 11.540895
Joined March 2009
- Tweets40
- Following108
- Followers516
- Likes25
Interested in working on memory-related problems (optimized usage, garbage collection, security, performance)? Directly apply or feel free to DM me.
You’re unable to view this Post because this account owner limits who can view their Posts. Learn more
Slides and video for my #BlinkOn9 talk on unifying Blink and V8 garbage collection slidr.io/mlippautz/towards-a… youtube.com/watch?v=9CukfHGu…
hej @conc_at #concat18, thanks for having me! 🔥 Slides for my talk "Live and let die: Untangling the web of objects" are available here: docs.google.com/presentation…
Michael Lippautz retweeted
Next day, next talk: @mlippautz from Google's V8 and Chromium team in Munich is giving you all the insights about how JavaScript connects to the DOM.
bit.ly/2De8I70 #concat #conference #web
Michael Lippautz retweeted
Big day for V8! We officially announced our intent to fully ship Ignition and TurboFan in V5.9 (Chrome M59 Stable)! v8project.blogspot.de/2017/0…
Michael Lippautz retweeted
Heads-up: We're planning to turn the new compiler architecture - based on I+TF - on by default soonish in Chrome! v8project.blogspot.de/2017/0…
Michael Lippautz retweeted
Big JS heaps and nice debugging story for memory leaking web apps v8project.blogspot.de/2017/0…
Step by step instructions on how to trace V8 statistics (call and heap) from within @googlechrome docs.google.com/presentation…
too much light makes the baby go blind @sfneofuturist – at SoMa, San Francisco
http://www.boston.com/bigpicture/2010/07/oil_spill_in_dalian_china.html #oilspill
Michael Lippautz retweeted
GoGo - a self-hosting Go compiler. Very nice! #golang








