i’ve been reading the excellent Web Browser Engineering recently and following along in #rustlang ^.^ so far we have a rudimentary html parser, dom tree, layout tree, and paint, in 1595 lines of rust:

Chapter 15 is here! Images and iframes introduce performance and security concerns that impact browser architecture, but they also build on and extend existing concepts like event loops, rendering, and accessibility in an elegant way. browser.engineering/embeds.html (c/p from Mastodon)

Chapter 16 is here! Invalidation is a key technique all major browsers use to make for fast rendering and smooth interactions, but it’s also famously difficult. This chapter explains how to make it work right. browser.engineering/invalidation.h…

WBE is almost done! We just published What Wasn't Covered, with all of the other parts of a browser that we just couldn't fit in. And there's also a post-script and a new glossary, all working toward publishing on paper sometime soon. Stay tuned! browser.engineering/skipped.html

After my last post, many folks reached out to understand in-depth technical details of browsers. I would suggest going through browser.engineering book. It is an incredible resource and gives a structured approach. Highly recommended!

Hello all! Web Browser Engineering will be coming out with Oxford University Press sometime in 2024. More details to come! browserbook.substack.com/p/publishing-w…

Wanna learn how to build a browser from scratch? Check out browser.engineering by Pavel Panchekha and Chris Harrelson 🤓🌐📘 In this (free) book, you build a "basic but complete web browser, from networking to JavaScript, in a couple thousand lines of Python"

Implemented chapter 2 of Web Browser Engineering . Added basic GUI using Tkinter to the toy browser with features like scrolling using mouse and up/down keys, line break etc. Github: github.com/ArunRawat404/B… #buildinpublic

Day 1 report: ML: finish the revision of probability and submit my first kaggle notebook DSA: recursion almost complete. Abdul bari explains the concepts like no one Project: Stuck at chapter 3 of Web Browser Engineering . Formatting text is really hard

Code report: Day 5 Browsey: Implement the chapter 5 of Web Browser Engineering. Now the logic has become very complicated. So, I decided to read this book in a research paper way. DSA: Solved the 3 problem. I get the more clarity in my head for dsa now. Logic will get better with time.

We've changed our logo to match the upcoming publication of Web Browser Engineering! You can pre-order it now: global.oup.com/academic/produ…

You can now pre-order Web Browser Engineering: global.oup.com/academic/produ… You should get it before the end of the year, perhaps as a present for your wintertime holiday of choice!

We've been reading the final proof of Web Browser Engineering. I'm amazed: it is 512 pages long, way longer than it felt while writing it. Publication is getting closer by the day!

Web Browser Engineering browser.engineering/index.html Web Browser Engineering

Hello new subscribers and thank you for the HN front page yesterday! We're super excited to see so many people becoming interested in web browser engineering.

Really excited to share that we've finished proofs of the Web Browser Engineering and the book is now moving into production. I can't wait to hold a physical copy! browserbook.substack.com/p/final-proofs…

Just received our copies of the hardcover edition. They feel light, are easy to read, and look great! Really excited to see these shipping out to pre-orders soon.

Just discovered this little gem - Web Browser Engineering, thanks to Robin Sloan This might just be the best book about Web Browsers ever written, and the site is a freakin' masterpiece 🖼️ Take my money - pre ordering now! 💸

Pavel Panchekha Web Browser Engineering Together, these two are the best and most authentic browser books.