1
The cost of parsing JSON
The dominant costs of processing JavaScript are download and CPU execution time.
V8 Blog
V8 is Google’s open source high-performance JavaScript and WebAssembly engine, written in C++.
- Popular posts
- 17
- Total points
- 4,815
- HN comments
- 2,524
- Rank
- #226 company
Visit v8.dev → RSS feedOn Hacker News Dec 2018 – Aug 2025
Web & Frontend 11Systems & Performance 10Software Engineering 8Security & Privacy 3Math & Algorithms 1
2
A lighter V8
The V8 Lite project dramatically reduced the memory overhead of V8 on typical websites, this is how we did it.
3
How we made JSON.stringify more than twice as fast
This post explains our recent effort to improve JSON.stringify performance
4
Faster JavaScript Calls
Faster JavaScript calls by removing the arguments adaptor frame
5
V8: A Year with Spectre
The V8 team details their analysis and mitigation strategy for Spectre, one of the top computer security issues of 2018.
6
JIT-Less V8
V8 v7.4 supports JavaScript execution without allocating executable memory at runtime.
7
V8 Sparkplug – A non-optimizing JavaScript compiler
In V8 v9.1 we’re improving V8 performance by 5–15% with Sparkplug: a new, non-optimizing JavaScript compiler.
8
The V8 Sandbox
V8 features a lightweight, in-process sandbox to limit the impact of memory corruption bugs
9
Retrofitting Temporal Memory Safety on C++
Eliminating use-after-frees vulnerabilities in Chrome with heap scanning.
10
Up to 4GB of Memory in WebAssembly
Thanks to recent work in Chrome and Emscripten, you can now use up to 4GB of memory in WebAssembly applications. That’s up from the previous limit of 2GB. It might seem odd that there was ever a limit - after all, no work was needed to allow people to use 512MB or 1GB of memory! - but it turns out that there are some…