How open sourcing Netscape Communicator in 1998 and the creation of Mozilla, a gamble at the time, paved the way for the now-mainstream embrace of the practice
A gamble 20 years ago unleashed the source code for the browser that became Firefox. The approach is now core to Facebook, Google and everyone else.
Context & Ripple Effects
Twenty years on, CNET marks the anniversary of the moment Netscape released Communicator's source code — the decision that created Mozilla and eventually Firefox, and that read as a desperation play at the time. The retrospective lands in an industry where the gamble has fully paid off as strategy: Microsoft had become GitHub's most prolific open-source contributor by 2016, and by 2019 open-source startups were drawing big VC rounds and multi-billion-dollar exits.
The irony the coverage surfaces is that the browser born from that openness is now the vulnerable party. Chrome and its open-source Chromium sibling power most new browser projects, giving Google effective leverage over the web, while Mozilla — per CEO Mitchell Baker's testimony in US v. Google — found that losing default placement crippled Firefox on mobile.
First-order effects
- The immediate legacy is organizational: the open-sourced Communicator code became Mozilla, which shipped Firefox, and Facebook, Google and the rest of the industry adopted the release-the-source playbook as standard practice rather than last resort.
Second-order effects
- Openness became a competitive weapon in reverse: because Chromium is free and open, rivals building on it cede browser-engine direction to Google, the exact concentration of power the 1998 move was meant to prevent.
- Mozilla's dependence on search-deal revenue — the arrangement Baker says degraded UX when Firefox switched to Yahoo in 2014 — shows that open-sourcing code solved distribution but not business model, pushing Mozilla toward diversifying revenue through browser personalization.
Third-order effects
- If the pattern holds, open source is no longer a moat or a gift but infrastructure whose governance matters more than its license: whoever steers the shared project — as Google does with Chromium — sets the platform's terms, making project stewardship the new gate to contest.
- The funding side points the same way: with VCs treating open-source companies as exit-worthy businesses, the 1998 framing of openness versus commerce has collapsed into openness as the commercial default.
The trend: Open source has traveled from Netscape's defensive gamble to the industry's default strategy — and the battleground has shifted from whether code is open to who controls the open project.