







I wrote most of this post sometime in 2022 but I think it holds up alright in 2024 so I decided to publish it for posterity. I don’t really like doing posts like this—I’d much rather share some innocuous learnings or tips but it turns out I have opinions too 😓 Sorry! 2024-02-21: I’ve added a few reflections at the end of the post. 2024-04-27: Developpez.com has produced a French translation of this post. Since I quit Mozilla and went back to full-time Web development, I’ve discovered a few surprises. It turns out Web development is actually pretty hard, Web developers are actually very smart, and some of these frameworks and techniques we mocked as browser engineers aren’t so bad. Oops. At the same time, it turns out some Web developers have ideas about browsers and the Web that, as a former browser engineer and standards editor, I’m a bit dubious of. Here are a few of the things that surprised me.
David Baron's weblog: How browser developers should seek feedback from Web developers
We were having a discussion about how browser developers should seek feedback from Web developers about the evolution of Web technology and the specifications that define it. I suggested the following list of things that browser developers should do, and Anne thought it was worth blogging:
The Elephant in the Room: Web design work is drying up | Hacker News
- A "web designer" or "web developer" used to be a generalist who wrote HTML, CSS, and some jQuery. Now there's a demand for specialization: a UI/UX designer who can prototype, iterate quickly, and use real data if possible, and a UI/UX engineer who can develop large-scale apps with an eye towards security, performance, reusability, and maintainability.
The reckless, infinite scope of web browsers
This blog post was published on March 18, 2020. It might be out of date, have broken images or links, or simply contain bad ideas and opinions that didn't stand the test of time. Please read generously!

The Fathers of the Internet Revolution Urge Today’s Software Engineers to Reinvent the Web
Tim Berners-Lee, Vint Cerf, and other Internet pioneers issue a challenge on a day that just might go down in tech history

Building The Next Web
This is the kick-off post in a series in which I'm going to explore things that we could change about the Web. The odds are pretty good that I will be wrong, possibly even very wrong. You're going to dislike some, or perhaps all of it! My point isn't to jump straight into building these ideas — even though I do believe they point in a better direction and are feasible — but rather to break out of the incrementalist rut and stagnant vision that the Web finds itself mired in. It's not in a good place and I feel the need for more vision work and much more thinking about architectural interventions that can bring about radical change.


How might a browser be developed?
There’s a confluence of things that have happened recently that have made me question how browsers might be developed: On January 8th 2026, Simon Willison predicted that someone will build a browser using mainly AI-assisted tools within 3 years On January 27th 2026, one human and one agent built a browser from scratch (great experiments) On the 19th February 2026, news came out that Taalas had a chip that can spit out nearly 17,000 tokens per second by baking a model onto the chip. I would like to indulge in a little bit of projection and in my case, some science fiction of my own.

Web Crypto’s SubtleCrypto: A Masterclass in Developer Hostility and How It Strangles the Modern Web
Not Subtle, Just Sabotage — An API Against the Web
Tailwind, and the death of web craftsmanship • pdx.su
There's a worrying trend in modern web development, where developers are throwing away decades of carefully wrought systems for a bit of perceived convenience. Tools such as Tailwind CSS seem to be spreading like wildfire, with very few people ever willing to acknowledge the regression they bring to our field…

WebAssembly’s post-MVP future: A cartoon skill tree – Mozilla Hacks - the Web developer blog
People have a misconception—they think that the WebAssembly that landed in browsers back in 2017—is the final version. In fact, we still have many use cases to unlock, from heavy-weight ...

The Better Web / The Human Web / The Living Web
A response to Aaron Parecki's response: on the false dichotomy of rewriting with Claude or shutting down, why 'understanding matters more than tools' sever…

When is the right time to share our excitement about new web features? | Rachel Andrew
When we share content about emerging web platform features, we have to be careful that we aren’t frustrating people with things they can’t use yet. However there is a place for talking about new things, and people who enjoy hearing about them. This post is about some of the ways I try to meet the needs of a browser DevRel team that need to share information about new things, with those of developers who need to know what actually works now. If you write or speak about the web, perhaps some of these ideas will help you too.
Design for Developers — Web Witch
A companion site for the Design for Developers book, rebuilt to practice the fundamentals the book teaches.

Web Engines Hackfest 2025
Building the Future of Work: A Year in Review with HERE Enterprise Browser
2024 was a year of significant transformation for HERE – literally. Anchored by the debut of our new brand and identity and the exciting launch of our HERE Enterprise Browser – the world’s first browser purpose-built for work – we reinforced our commitment...
