Firefox, which is 100% open source, has a critical security advantage over all other browsers
Trust but Verify — Background — It is becoming increasingly difficult to trust the privacy properties of software and services we rely on to use the Internet.
Context & Ripple Effects
Brendan Eich's 'trust but verify' argument lands at the end of a long-running arc: since Firefox began eroding Internet Explorer's dominance in 2005 (the browser race coverage framed it as the frontrunner), the case for Firefox has mostly been made on speed and standards. Here the pitch changes register — the advantage is not what Firefox does but that anyone can check its fully open-source codebase.
The timing matters because the piece opens from a premise that trust in software is getting harder, not easier — and because Mozilla has carried a known conflict-of-interest question for years via its Google search revenue relationship (flagged back in 2007). The open-source claim is Eich's answer to that vulnerability: even where Mozilla's incentives are questioned, the code remains inspectable.
First-order effects
- The argument hands Firefox a differentiation axis that Chrome, Internet Explorer and Safari cannot match outright while their full stacks stay closed, forcing those vendors to compete on transparency rather than just performance or distribution.
- Users evaluating browsers after a stretch of privacy scares gain a concrete selection criterion — verifiable code — shifting the comparison from feature checklists to auditability.
Second-order effects
- Rivals' likely response is selective openness — releasing components or audits without opening everything — which invites exactly the scrutiny Eich's framing sets up: partial transparency gets read as a concession that the rest needs hiding.
- Mozilla's own dependence on Google revenue keeps the attack surface open; expect critics to test whether 'verifiable code' neutralizes the conflict-of-interest critique or merely coexists with it.
Third-order effects
- If verifiability becomes a buying factor, browser competition reorganizes around trust infrastructure — who can prove what their software does — rather than around rendering benchmarks, a structure that favors projects with genuinely open codebases.
- The deeper pattern is trust migrating from vendor reputation to inspectable artifacts; whether meaningful numbers of users or auditors actually verify the code, or the claim works purely as a signal, is the genuine uncertainty in how far this goes.
The trend: Browser competition is adding a trust-and-verifiability dimension alongside the traditional speed-and-standards race, with full open-source status as the hardest-to-copy position.