Web Browser Engineering (2021)
ibobev
149 points
20 comments
November 17, 2026
Related Discussions
Found 5 related stories in 205.5ms across 13,334 title embeddings via pgvector HNSW
- Anatomy of a Browser syumei · 11 pts · September 03, 2026 · 62% similar
- Show HN: Browser Tools SDK – an optimal browser harness for agents tanishqkanc · 11 pts · July 21, 2026 · 59% similar
- Show HN: Watching browser fingerprinting calls via Chromium's Blink layer brnbs · 11 pts · August 10, 2026 · 58% similar
- The bitter lesson of browser agents gregpr07 · 11 pts · September 15, 2026 · 56% similar
- Modern Web Guidance 1.0: The web platform expertise your coding agent is missing qainsights · 29 pts · November 11, 2026 · 56% similar
Discussion Highlights (6 comments)
sublinear
> On top of all of that, modern browsers also execute WebAssembly, a hardware-independent bytecode format for many other programming languages to target, and which may one day be co-equal to JavaScript on the web. I skipped around a bit, but when I stumbled onto this opinion I backed out. This is not the point of wasm at all. Wasm is there as a compatibility layer and for squeezing extra performance out of critical sections of code. The decisions to restrict its API access are very sensible. We can't honestly still be confused about this in 2026. I excused the python code since a serious browser is not the point, but I'm now suspicious of other intuition-building done throughout the rest of the book.
pavpanchekha
Hi folks, one of the authors here. Happy to answer questions. Chris and I wrote the book starting in 2019, and the book was largely done in late 2024, with publication in 2025. In case folks are wondering, literally none of it was AI-written, because the AIs didn't exist yet!
TZubiri
pangram says not LLM Congratulations on not slopping out
coreyp_1
Nice. I'm on the path to building a browser. I had vaguely remembered this site from when it was listed before, but I couldn't find it when looking again. It's bookmarked now. :) I'm writing my own libraries (because, with AI, why not indulge in low-level fun?), and I'm almost to the layout engine. So far (all C libraries), I can read multiple image formats, parse HTML/XML and CSS, rasterize text and just about anything that can be required by CSS or SVG. Fonts were fun... I can do TTF but not WOFF yet. I can do some WASM, but no JS engine yet. I do have my Regex engine, though. (I had built WASM first because it's being used for another project). Still a long way to go. Only approx 780K lines spread out across 30 or so libraries written so far.
kuharich
Past comments: https://news.ycombinator.com/item?id=26707368 , https://news.ycombinator.com/item?id=28898157 , https://news.ycombinator.com/item?id=41846780
NooneAtAll5
who tf thought .engineering should be allowed to be a TLD?