how browsers work
Learning and science
interactive guide
SHOW HN2026
How HN took it
8 positive, 7 neutral or asking, 0 mixed, 6 critical, out of 21 comments about the project. Thread score +0.11.
Docs: 2 for, 5 againstDesign: 1 for, 1 againstIdea: 2 for, 0 against
The thread, comment by comment
Each row is a top-level comment and its replies, in HN's order. Select a cell to open that comment on HN.
positive neutral or mixed critical about another commenter or something else the maker
What HN said
What people liked
Clear, interactive mental model for browser internals
From 3 comments
I love the "mental model" approach here. Most guides I've seen either get bogged down in the minute details of TLS/Handshakes immediately or are way too high-level. The…
A1aM0 on HNCool project, thanks for sharing. HN readers should also check out https://hpbn.co (High-Performance Browser Networking) and https://every-layout.dev (amazing CSS resource; the…
chrisweekly on HNThis is cool
raghavankl on HN
Useful for learning how browsers work, like a modern TV-electronics book
From 2 comments
When I was a kid I had an electronics book about how (CRT based) TVs work. Posts like this are the modern version of that.
amelius on HNNeat, it's like an exciting way to dive into https://browser.engineering without having anything to install. I'm wondering if examples with Browser/Server could benefit from a…
utopiah on HN
Objections
Network requests take up too much of the guide versus parsing and rendering
From 1 comment
Bit unfortunate that more than half of the page is dedicated to network requests, but almost all work and complexity of the browser is in the parsing and rendering pipeline.
edwinjm on HN
DOM history and terminology is inaccurate or oversimplified
From 2 comments
Not all browsers had or have a DOM, and some didn’t until later versions. Early browsers without DOMs (with initial release date): WorldWideWeb (Nexus) (Dec 1990), Erwise (Apr…
domnodom on HN> Would be writing something like "DOM in the modern browsers" more correct then? No, I don't think so. I don't know why the GP comment is at the top beyond historical interest.…
magicalist on HN
URL handling guess behavior is oversimplified
From 2 comments
Claims that browsers transform "d.csdfdsaf" -> https://d.csdfdsaf, but they don't. They only transform domains with valid TLDs, unless you manually add the URL scheme.
LoganDark on HNThe "guesswork" done by browsers is actually pretty nuanced and not standardised in a slightest way. Some defaults are pretty common, and could be maybe considered de-facto…
myfonj on HN
Covers only Safari and Chrome, not all browsers
From 1 comment
This doesn't account for all browsers, only Safari and Chrome. There isn't even a passing mention of separate search and address bars.
GaryBluto on HN
Requests
Cover rendering, layout and reflow in more detail
From 2 comments
Great project, thanks What's your next steps, do you plan to add more details of the reflow process?
englishcat on HNWill cover the rendering engine in more details. I didn't know at what sections to go deeper. So just stopped and published it to gather more feedback. Thank you!
krasun on HN
Explain how images, styles and scripts load
From 1 comment
I like it very much --> bookmarked :-) The step I am missing is how other resources (images, style sheets, scripts) are being loaded based on the HTML/DOM. I find that crucial…
arendtio on HN
Fix narrow-window layout where contents overlaps
From 1 comment
For a narrow browser window (< 1170) the contents section floats over the contents which is distracting
philk10 on HN
Add browser/server visual icons
From 1 comment
Neat, it's like an exciting way to dive into https://browser.engineering without having anything to install. I'm wondering if examples with Browser/Server could benefit from a…
utopiah on HN
Questions
How does the DNS section account for HTTPS resource records
From 1 comment
Perhaps worth editing the DNS section in light of RFC 9460 ... depending on the presence and contents of the HTTPS RR, a browser might not even use TCP. Here's a good blog post…
jeffbee on HN
Alternatives named
browser.engineering
From 1 comment
Neat, it's like an exciting way to dive into https://browser.engineering without having anything to install. I'm wondering if examples with Browser/Server could benefit from a…
utopiah on HN
High Performance Browser Networking
From 1 comment
Cool project, thanks for sharing. HN readers should also check out https://hpbn.co (High-Performance Browser Networking) and https://every-layout.dev (amazing CSS resource; the…
chrisweekly on HN