1012: Who Decides What Ships on the Web?

Jake Archibald shares his extensive experience navigating the web standards landscape, from his start at the BBC to his decade at Google and now his role at Mozilla. He discusses how his work on APIs like service workers, view transitions, and linear easing in CSS has shaped his perspective. The conversation highlights the differences in organizational resources and priorities between Google and Mozilla, emphasizing Mozilla's agility and focus on impactful standards. Jake also reflects on how feedback from developers influences browser features, and about Mozilla's transparent process for measuring community interest via GitHub signals.

The episode delves into how web browsers decide what features to implement, emphasizing the importance of web compatibility and community feedback. Jake talks about the significance of precise priorities—such as ensuring sites don't break in Firefox—and the challenges in managing feature backlogs. They discuss specific APIs like the Heading Offset API, which solves practical problems like heading hierarchy management in complex web projects, and the role of developer signals and community input in shaping the browser's development pipeline. The episode also covers the internal debates about features like cross-document view transitions and the importance of progressive enhancement.

A significant part of the discussion centers around the controversial Prompt API — an API allowing in-browser large language models, which raises concerns about non-determinism, privacy, consent, and influence from corporations like Google. Jake elaborates on how this API could be misused or co-opted, and the risks of designing standards that benefit large companies at the expense of web neutrality. The conversation considers whether local models could be a safer, more private alternative, and debates the cost-benefit of rapid adoption versus careful standards. Additionally, discussions about AI features, translation tools, and the importance of transparent, developer-centered API design highlight the complexities of integrating AI into web standards responsibly.

Jake emphasizes Mozilla's cautious but progressive stance on new features, advocating for APIs that are predictable and secure while enabling innovative capabilities like WebGPU, popovers, and view transitions. Mozilla's process involves active engagement with the developer community via signals and feedback repositories, avoiding hype-driven decisions. The episode discusses Mozilla's resistance to certain APIs like Web Bluetooth and Web MIDI due to security concerns but also their willingness to adjust based on user and developer demand. The importance of transparency in browser development and user control over features like AI translation and web APIs is a recurring theme, reinforcing Mozilla's commitment to an open, equitable web.

The conversation explores the strategic landscape of browser vendors, with Jake pointing out Google's push for rapid feature deployment often at the expense of interoperability and community input. Mozilla, Microsoft, and WebKit are working to maintain a fair and open process, emphasizing the importance of community signals and careful prioritization. The episode touches on the potential and risks of browser APIs like WebGPU, Web Serial, and experimental features like in-browser AI, balancing innovation with security and user trust. Overall, the discussion underscores the importance of collaborative standard-setting and listening to developer feedback to ensure the web remains inclusive, secure, and accessible for the future.