AI Summary
5 min readJake Archibald spent a decade at Google as a Chrome DevRel, working on service workers, fetch, view transitions, and the linear easing function in CSS. After a stint at Shopify, he returned to browser standards work at Mozilla, where he now serves as a Firefox DevRel. On this episode of Syntax, he walks through what it means to be a small-engine browser in a world where Chrome sets the agenda, why the Prompt API worries Mozilla, and how Firefox decides what to build next.
The Uneven Playing Field of Browser Engines
Firefox is one of only three browsers that maintains its own engine (the others being Chrome’s Blink and Safari’s WebKit). Every other major browser—Edge, Opera, Brave, Samsung Internet—runs on Chromium. That leaves Mozilla in an asymmetric position. “It’s not a browser owned by a billionaire,” Archibald notes, contrasting Firefox with its competitors. Despite that resource gap, he remains impressed by how much the team ships. “Sometimes we are last on features, but a lot of the time we're second or even first.” Recent examples include the Sanitizer API, the Temporal API, and heading offset. On features like style container queries, Firefox was last—but that’s the nature of triage.
Continue reading the full summary in the app — free to try.
Read Full Summary →Free • No credit card required
Never miss an episode of Syntax - Tasty Web Development Treats
Get every new episode summarized in your inbox — free, ~5 minutes to read.
No spam. Unsubscribe anytime.
What you'll learn
- 1 (00:00) **Sunburn Story & Guest Intro** - Scott tells a story about getting sunburned during a shoot, then introduces guest Jake Archibald.
- 2 (03:16) **Jake's Background & Transition to Mozilla** - Jake shares his career path from BBC, Google, Shopify, and now Mozilla doing DevRel.
- 3 (06:54) **Mozilla's Current State & Priorities** - Jake discusses Mozilla's resources, engine independence, and how they decide what to implement.
- 4 (09:54) **Developer Signals & Interop Survey** - Jake explains how Mozilla uses developer feedback, including a survey for Interop 2026.
- 5 (13:20) **Deep Dive: JPEG XL vs. AVIF** - Jake explains JPEG XL and AVIF image formats, their trade-offs, and progressive rendering.
- 6 (18:03) **Firefox: End-User Features vs. Web Features** - Clarifying that different teams handle engine features versus browser UI features.
- 7 (20:57) **The Prompt API Controversy** - Jake explains the Prompt API, Chrome's push for it, and Mozilla's objections.
+ Full timestamped outline available in the app
Show Notes
Scott and Wes sit down with Jake Archibald from Mozilla to unpack how web standards actually get made at Firefox. From browser features and developer feedback to the drama around the Prompt API. They discuss Interop 2026, the future of web APIs, and what it’s really like shaping the web after a career spanning both Google and Mozilla.
Show Notes
- 00:00 The Importance of Sunscreen
- 02:29 Welcome to Syntax!
- 04:35 Transitioning from Google to Mozilla
- 06:00 Brought to you by Sentry.io
- 06:43 Mozilla’s Current Position and Development Priority
- 08:35 Feature Implementation and Developer Feedback
- 13:12 JPEG XL and AVIF: The Future of Image Formats
- 18:06 Balancing User Features and Web Standards
- 20:56 Navigating the AI Translation Dilemma
- 23:03 Understanding the Prompt API Controversy
- 32:56 Rethinking the Future of Prompt APIs
- 39:00 Exploring Local Models and User Control
- 44:04 The State of Firefox DevTools
- 45:42 Browser Stability and Developer Editions
- 47:39 Introduction to the Heading Offset API
- 51:14 Interop APIs and Their Importance
- 54:10 Developer Feedback and Browser Features
- 58:05 Animating Display None and Its Challenges
- 01:00:44 HTML and Canvas: Opportunities and Concerns
- 01:04:01 Sick Picks + Shameless Plugs
Sick Picks
- Scott:
- Wes:
- Jake:
Shameless Plugs
More from this podcast
Syntax - Tasty Web Development Treats →