Web Browser Engineering (2021)

(browser.engineering)

71 points | by ibobev 1 hour ago

6 comments

  • pavpanchekha 55 minutes 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!
  • omegaSigma95 55 minutes ago
    [flagged]
  • nophonobaldi 48 minutes ago
    [dead]
  • TZubiri 46 minutes ago
    pangram says not LLM

    Congratulations on not slopping out

    • pavpanchekha 42 minutes ago
      The book was written between 2019 and 2024, and published in 2025!
  • sublinear 1 hour ago
    > 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 53 minutes ago
      Hi, author here! I made a real effort to keep opinions out of the book, and I'm wondering what you feel is opinion above! I don't mean to imply that WebAssembly either will or should be co-equal to JavaScript, just that 1) it's not covered in the book at all, and 2) who knows what the future will contain.

      In any case, this line is in the appendix describing what we didn't cover and, per that, we don't say anything else about WebAssembly in the book!

      • enos_feedler 38 minutes 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
    • suriyaG 57 minutes ago
      what do you find about this opinion to be a problem?

      I've worked with wasm and am fairly familiar with the ecosystem. it sounds like it captures the essence quite well

    • msla 44 minutes 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's completely inaccessible! I mean, it's completely non-discoverable! I mean, it's completely UI/UX Compliant because it will be Mystery Meat Navigation from The UI/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.

      You know the people who thought Java Applets, Flash, and Sliverlight were Wonderful Ideas would be on top of that one.