We're on the brink of another world browser war
Based on Fireship's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.
Browser market concentration (over 90% across major browsers) increases the risk that centralized control over shared technology and funding could affect internet openness.
Briefing
Web browsers are becoming a strategic chokepoint for the open internet, and the rise of independent, open-source engines like Ladybird is framed as a hedge against centralized control. With Chrome, Safari, Edge, and Firefox together commanding over 90% of market share—and with much of the underlying technology and funding tied to Google—control over browser infrastructure could translate into control over what content can be accessed or suppressed. The transcript argues that even if Google’s intentions are benign, the concentration of leverage means the internet’s openness is vulnerable to hypothetical shifts in incentives.
Against that backdrop, the discussion spotlights Ladybird, a “futuristic” open-source browser project built from the ground up rather than assembled on top of Chromium. The origin story traces back to Andreas Kling, a software engineer who previously worked on WebKit at Apple and Nokia. After a period of unemployment and boredom following a three-month Swedish rehab program, Kling began building a new operating system and browser stack—an effort that later became Serenity OS. In 2022, Serenity OS’s browser engine declared independence as a cross-platform project, and the browser was renamed Ladybird. The project has grown to around 1,000 contributors, with roughly half a million lines of C++ code, and it has since attracted organizational backing through a nonprofit formed with a GitHub co-founder.
A key differentiator is governance and incentives: the nonprofit is funded entirely by sponsorships and donations, and the code is described as fully free and not borrowing from other browsers. That “no incentives” framing is used to contrast Ladybird with for-profit, Chromium-based privacy browsers such as Brave, which still rely on Google’s Chromium foundation. The transcript treats this independence as more than a technical preference—it’s positioned as a structural safeguard for the internet’s future.
Timing is the tradeoff. The first alpha releases for Linux and macOS are not expected until summer 2026, and a Windows version is implied to be even farther out. Still, developers can experiment by building from source on GitHub. The transcript emphasizes why the timeline is long: browser engines must implement and continuously track W3C standards that span millions of words and evolve rapidly. It also notes that modern browser development is a multi-stage loop—make it work, make it good, make it faster—using custom implementations of HTML and JavaScript engines (named libHTML and lijs) and established tooling such as FFMPEG for media.
The closing message ties the engineering effort to a broader political concern: as online power consolidates, independent browser engines may become a practical last line of defense—whether for preserving access, resisting censorship, or simply keeping the internet’s culture from being narrowed by centralized control.
Cornell Notes
The transcript frames browser engines as a critical point of control over the open internet, because the dominant browsers share technology and funding structures tied to Google. In response, it highlights Ladybird, an open-source browser project built independently rather than on top of Chromium. Ladybird traces back to Andreas Kling’s earlier work on Serenity OS, with the browser engine spinning out as a cross-platform project in 2022 and later renamed Ladybird. The project is organized as a nonprofit funded by sponsorships and donations, aiming to avoid “bad incentives” and keep the code free and not borrowed from other browsers. The catch is speed: early alpha support for Linux and macOS is expected in summer 2026, reflecting the extreme complexity of implementing evolving W3C standards.
Why does the transcript treat browser engines as an “existential threat” to internet openness?
What is Ladybird, and how did it originate?
What makes Ladybird’s approach different from Chromium-based browsers like Brave?
What timeline constraints does the transcript highlight for Ladybird releases?
Why is building a browser from scratch so difficult?
Review Questions
- How does market share concentration translate into potential control over what users can access on the internet?
- What role do W3C standards play in determining how long it takes to build and maintain a browser engine?
- What governance and code-independence choices does Ladybird make, and why does the transcript treat those as strategically important?
Key Points
- 1
Browser market concentration (over 90% across major browsers) increases the risk that centralized control over shared technology and funding could affect internet openness.
- 2
Ladybird is positioned as a hedge against that risk by building an independent, open-source browser engine rather than relying on Chromium.
- 3
Andreas Kling’s background (including prior work on WebKit at Apple and Nokia) feeds into Ladybird’s technical lineage from Serenity OS.
- 4
Ladybird’s nonprofit funding model relies on sponsorships and donations, aiming to reduce incentive-driven compromises.
- 5
The project’s independence is emphasized through claims that the code is free and does not borrow from other browsers, unlike Chromium-based privacy tools such as Brave.
- 6
Browser development is slow because W3C specifications are massive (millions of words) and constantly changing, requiring continuous implementation work.
- 7
Early Ladybird alphas for Linux and macOS are expected in summer 2026, reflecting the complexity of building and optimizing a full browser stack.