Mozilla Firefox: How we make sh*t Work
summary
Firefox claims performance parity with Chrome after Firefox 57 (Quantum) faster than Chrome and serves 330 million active users; engineering relies on Rust and Gecko, migrated from CVS to Mercurial, and ships changes to a massive user base. Remote, async work uses video conferencing plus tools like Bugzilla, GitHub, Trello, Fabricator, MediaWiki (MDN) and Smartsheet. Process-wise teams run 2–3 week sprints, 30-minute kickoffs, cross‑functional backlog grooming and aim for features scoped across three iterations; tracking protection on by default is a current product priority.
AI-written summary · about
chapters (11)
- 0:00Introduction to Firefox
- 1:47What is Firefox today
- 3:12Why Firefox lagged behind Chrome
- 5:00Firefox Quantum and revival
- 6:06Mozilla’s open-source legacy
- 9:38Mike’s role at Mozilla
- 11:29Organizational challenges
- 14:42Async workflow solutions
- 18:36Open culture and manifesto
- 20:46Agile but different process
- 23:34Q&A and closing
related talks
35mAvoiding the Petard: Triage at Scale in Firefox Quantum
33mBrowser Extensions
43mCleaning the Tar: Using React within the Firefox Developer Tools
01h 44mFirefox Bug Rodeo!
31mDebugging Your Debugger
35mYour Browser Is Your Best Friend for Web Development
29mOur web development workflow is completely broken
37mEverything Web and Why Open Matters