8 comments

  • pavpanchekha3 hours ago
    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!
    • callc1 hour ago
      Hey Pavel! Thank you so much to you and Chris for writing this book. I really mean it! It&#x27;s started me on a fun journey (and hopefully career change soon) into working on really hard problems in browsers.<p>I finished going through this in July this year. Here are my thoughts at the time: <a href="https:&#x2F;&#x2F;calvinlc.com&#x2F;p&#x2F;2026&#x2F;07&#x2F;23&#x2F;browser.html" rel="nofollow">https:&#x2F;&#x2F;calvinlc.com&#x2F;p&#x2F;2026&#x2F;07&#x2F;23&#x2F;browser.html</a><p>No questions, just gratitude!
    • shoobiedoo57 minutes ago
      Amazing work. I&#x27;ve always heard that browsers are more complex than operating systems but I never thought to investigate how that could be. Your book shows the layers beautifully
  • coreyp_11 hour ago
    Nice.<p>I&#x27;m on the path to building a browser. I had vaguely remembered this site from when it was listed before, but I couldn&#x27;t find it when looking again. It&#x27;s bookmarked now. :)<p>I&#x27;m writing my own libraries (because, with AI, why not indulge in low-level fun?), and I&#x27;m almost to the layout engine.<p>So far (all C libraries), I can read multiple image formats, parse HTML&#x2F;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&#x27;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.
    • pavpanchekha1 hour ago
      That sounds incredibly fun. Hope you enjoy the book!
  • kuharich1 hour ago
    Past comments: <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=26707368">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=26707368</a>, <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=28898157">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=28898157</a>, <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=41846780">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=41846780</a>
  • omegaSigma953 hours ago
    [flagged]
  • TZubiri2 hours ago
    pangram says not LLM<p>Congratulations on not slopping out
    • pavpanchekha2 hours ago
      The book was written between 2019 and 2024, and published in 2025!
  • nophonobaldi2 hours ago
    [dead]
  • sublinear3 hours ago
    &gt; 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.<p>I skipped around a bit, but when I stumbled onto this opinion I backed out.<p>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&#x27;t honestly still be confused about this in 2026.<p>I excused the python code since a serious browser is not the point, but I&#x27;m now suspicious of other intuition-building done throughout the rest of the book.
    • pavpanchekha3 hours ago
      Hi, author here! I made a real effort to keep opinions out of the book, and I&#x27;m wondering what you feel is opinion above! I don&#x27;t mean to imply that WebAssembly either will or should be co-equal to JavaScript, just that 1) it&#x27;s not covered in the book at all, and 2) who knows what the future will contain.<p>In any case, this line is in the appendix describing what we <i>didn&#x27;t</i> cover and, per that, we don&#x27;t say anything else about WebAssembly in the book!
      • enos_feedler2 hours ago
        Perhaps nix the part about it being co-equal to JavaScript in the future. Im not sure its even a goal of wasm to get there and it just invites grumbles like parent over there
        • throawayonthe2 hours ago
          <a href="https:&#x2F;&#x2F;hacks.mozilla.org&#x2F;2026&#x2F;02&#x2F;making-webassembly-a-first-class-language-on-the-web&#x2F;" rel="nofollow">https:&#x2F;&#x2F;hacks.mozilla.org&#x2F;2026&#x2F;02&#x2F;making-webassembly-a-first...</a>
          • sublinear1 hour ago
            Not a link to a W3C decision. There have been drafts. They stayed drafts for a reason.
    • suriyaG3 hours ago
      what do you find about this opinion to be a problem?<p>I&#x27;ve worked with wasm and am fairly familiar with the ecosystem. it sounds like it captures the essence quite well
    • msla2 hours ago
      Hey, just imagine: Rustact, a React-a-like where you write the code in Rust and everything gets compiled to a massive blob of WASM to be rendered client-side. It&#x27;s completely inaccessible! I mean, it&#x27;s completely non-discoverable! I mean, it&#x27;s completely UI&#x2F;UX Compliant because it will be Mystery Meat Navigation from The UI&#x2F;UX Experts, and it will be so much more performant to shove a 100 MB blob down the line to everyone than have 10 10 kB blobs being served on-demand.<p>You know the people who thought Java Applets, Flash, and Sliverlight were Wonderful Ideas would be on top of that one.
      • CharlesW1 hour ago
        &gt; <i>It&#x27;s completely inaccessible! I mean, it&#x27;s completely non-discoverable!</i><p>Solutions like this can still render to DOM instead of Canvas. Here&#x27;s Rustact, but with Swift&#x2F;Swift UI: <a href="https:&#x2F;&#x2F;elementary.codes&#x2F;" rel="nofollow">https:&#x2F;&#x2F;elementary.codes&#x2F;</a>