Conclusions

With Chapter 16 done, it’s time for Chris and me to wrap up Web Browser Engineering. Of course, web browsers are massive, with tens of millions of lines of code, and if we wanted to we could probably keep writing new chapters forever. But to keep the book finite, we’ve put many of those ideas into a “What Wasn’t Covered” chapter that lists every chapter we thought of writing, and didn’t. I think it makes a good summary of what else goes into a browser implementation, and why these programs are such behemoths.

Since we’re not writing more chapters, we’re now working on wrapping up the book. You’ll see edits (including some major ones) to already-published chapters, and also technical changes to the code that we think will make it clearer. A lot of these involve back-porting changes from later chapters to earlier ones, and we’ll blog about them as they happen.

We’re also working on finishing up various related content in the book. We’ve just released a post-script, a glossary, and a one-page version of the book. We’re working on similar things too. That should set us up to publish a physical copy of the book sometime soon—stay tuned for an announcement.

Thanks as always to readers, and our supporters on Patreon. Please continue to give us feedback and tell your friends all about it. And follow this blog and Mastodon (or Twitter, whatever it might be called) to hear about future updates, and participate in the Github Discussions with questions and answers for the community.