Former Mozilla exec: Google has sabotaged Firefox for years (2019)

Original Article ↗ Hacker News Discussion ↗

A former Mozilla executive’s claim that Google has deliberately sabotaged Firefox to push users toward Chrome prompts broader scrutiny of how Google’s web services perform on competing browsers. Commenters debate whether issues like user-agent checks, artificial delays on YouTube, and weak cross-browser testing reflect malicious intent or structural bias inside a dominant platform company, while also criticizing Mozilla’s own strategic missteps and financial dependence on Google. The exchange underscores worries about a de facto Chromium monoculture, conflicts of interest when a browser vendor also controls major web properties, and the fragility of independent browser ecosystems.

Alleged Google Sabotage vs Incompetence

  • Many commenters report Google services (YouTube, Hangouts/Meet, Teams, etc.) working noticeably worse on Firefox than on Chrome.
  • Explanations split:
    • Some argue this is deliberate “sabotage” to keep Firefox share low.
    • Others say it’s more likely cultural/structural bias: Googlers build and test primarily in Chrome, so regressions on Firefox aren’t prioritized.

User-Agent Checks and Artificial Delays

  • Several reports describe Google properties behaving differently based on the browser’s user agent.
  • Examples include:
    • Historical cases where spoofing the user agent to Chrome made services run faster or bypass “unsupported browser” banners.
    • A recent YouTube case where a 5‑second delay is injected for non‑Chrome browsers, widely viewed in the thread as clearly anti‑competitive.

Testing Practices and Structural Bias

  • Some participants, including people claiming inside knowledge, say engineers use UA checks to route around Firefox bugs, then never revisit the slower path once Firefox improves.
  • Critics argue that failing to maintain robust cross‑browser automated testing at Google/YouTube is itself a form of anti‑competitive neglect, even if not consciously malicious.

Mozilla’s Decisions and Self‑Sabotage Claims

  • Many blame Mozilla for “sabotaging” itself:
    • Late adoption of multiprocess architecture and performance fixes.
    • Breaking legacy XUL extensions and mobile extensions, with promises some feel weren’t kept.
    • UI churn, bundled services like Pocket, and perceived misallocation of funds or leadership issues.
  • Others counter that:
    • Firefox’s old extension model made stability and security improvements hard.
    • The move to WebExtensions and killing Servo were painful but necessary within limited budgets.

Performance and User Experience Anecdotes

  • Experiences are highly mixed:
    • Some find Firefox slower, more memory‑hungry, or crash‑prone.
    • Others report the opposite: Chrome feels bloated, while Firefox is lighter; Safari often seen as fastest on macOS.
  • Several people keep Chrome/Chromium only for “broken” sites.

Market Power, Antitrust, and Browser Monoculture

  • Commenters highlight Google’s dominant web properties and financial relationship with Mozilla as a conflict of interest.
  • Concerns center on:
    • Chrome becoming a de facto IE6 replacement: “only works in Chrome” sites increasing.
    • Google using Firefox as an “antitrust beard” while undermining it in practice.
    • Fears that a Chromium monoculture lets whoever controls the engine “control the web.”