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
Bringing garbage collected programming languages efficiently to WebAssembly
A recent article on WebAssembly Garbage Collection (WasmGC) explains at a high level how the Garbage Collection (GC) proposal aims to better support GC languages in Wasm, which is very important given their popularity. In this article, we will get into the technical details of how GC languages such as Java, Kotlin…
6
JIT-Less V8
V8 v7.4 supports JavaScript execution without allocating executable memory at runtime.
7
JavaScript's New Superpower: Explicit Resource Management
The Explicit Resource Management proposal empowers developers to explicitly manage the lifecycle of resources.
8
What’s in that .wasm? Introducing wasm-decompile
WABT gains a new decompilation tool that can make it easier to read the contents of Wasm modules.
9
V8 release v7.2
V8 v7.2 features high-speed JavaScript parsing, faster async-await, reduced memory consumption on ia32, public class fields, and much more!
10
WebAssembly Tail Calls
This document explains the WebAssembly tail calls proposal and demonstrates it with some examples.
11
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…