Mozilla names new CEO as it pivots to data privacy

Original Article ↗ Hacker News Discussion ↗

Mozilla’s decision to replace longtime CEO Mitchell Baker with interim chief Laura Chambers has reignited scrutiny of the organization’s direction, finances, and stewardship of Firefox. Commenters question Baker’s multi‑million‑dollar compensation amid Firefox’s collapsing market share, layoffs, and heavy dependence on Google search royalties, while acknowledging her historic role in creating Mozilla and backing projects like Rust. Many express skepticism that a stated pivot to “data privacy” and AI will matter unless Mozilla refocuses on Firefox itself and its independence from the Chrome/Blink ecosystem.

Reaction to leadership change

  • Many welcome Mitchell Baker stepping down as CEO, describing it as long overdue and interpreting “stepping down” as a likely forced move; a minority emphasize her early, crucial role in creating Mozilla/Firefox and the open web.
  • New interim CEO Laura Chambers is viewed skeptically by some (corporate-speak announcement, LinkedIn link from a “privacy” org, prior role on the compensation committee), but others reserve judgment and hope she will refocus on Firefox.

Assessment of Baker’s tenure

  • Common criticisms: Firefox market share collapsed ~80–90% since 2008 while executive pay, especially Baker’s, rose several‑fold; 2020 layoffs (including core engineering/Rust teams) coincided with further CEO raises.
  • Defenders argue Firefox’s decline is largely due to Google’s massive distribution, marketing, and platform power, not simply mismanagement, and note Mozilla’s revenue and cash reserves actually grew.

Business model & dependence on Google

  • Consensus that Mozilla is heavily funded by search royalties, mostly from Google; many see this as a strategic trap that:
    • Limits how aggressive Firefox can be on ad‑blocking and anti‑tracking.
    • Discourages true product-market feedback because Mozilla is insulated from users’ payments.
  • Some suggest deals with other search providers or platform vendors were possible; others think the bargaining position was always weak.

Firefox’s decline and product direction

  • One camp argues Firefox was “neglected”: too many side projects (Firefox OS, VPN, Pocket, etc.), not enough visible innovation or UX polish in the core browser, slow on things like PWAs and certain web APIs.
  • Another camp says the browser itself has improved significantly (Quantum, privacy features, containers), and that distribution lock‑in and developer targeting of Chromium are the dominant factors.
  • Several developers say they’ve stopped testing for Firefox due to low usage, which reinforces its marginalization.

Rust, Servo, and technical contributions

  • Many credit Mozilla with a major positive legacy in Rust (and Servo), and consider that a rare, high‑impact achievement—even if it was later spun out and the internal teams were laid off.
  • Disagreement over how much current leadership deserves credit versus earlier technical leadership, and whether cancelling Servo was necessary or short‑sighted.

Privacy pivot & engine independence

  • Skepticism that a new “data privacy” pivot is more than branding; some point out Firefox already has strong privacy protections, others contrast it with Brave and Chromium forks.
  • Strong concern about a Chromium monoculture: several argue Firefox’s independent engine is strategically vital to keep the web from effectively becoming a Google‑controlled platform, even if it’s expensive to maintain.

Governance, pay, and structure

  • Widespread discomfort—even among some defenders—with a mission‑driven, quasi‑nonprofit structure paying a CEO ~1% of revenue while cutting engineering staff.
  • Proposals include: spinning Firefox into its own focused entity, imposing stricter norms on executive comp, and creating ways to fund Firefox directly rather than via broad “Mozilla” donations.