AI summary by TwinMind
There's A New Browser (That ISN'T Chrome Based)
Theo - t3․gg
47m 58s
Initial Browser Overview and Controversies
- New browser called Ladybird - built from ground up, not Chrome wrapper or Firefox fork
- Controversial history with maintainers from Serenity OS project
- 2021 PR controversy over grammatical corrections (changing "he" to "they")
- Maintainer Andreas Kling responded politically to innocent grammar fixes
- Eventually same changes merged when labeled as "grammar fixes" instead of gender-neutral language
- Pattern of maintainers "dying on hills" and pushing back on generally accepted practices
Ladybird Browser Initiative Launch
- New 501(c)(3) nonprofit announced with tax-exempt status pending
- Funded entirely by sponsorships/donations, no corporate deals or revenue streams
- Board directors: Andreas Kling (Serenity OS, Safari, Nokia webkit, khtml background) and Chris Wanstrath (GitHub co-founder/CEO)
- Target ship date: Summer 2026
- $1 million pledge from Chris Wanstrath's family to support development
Technical Architecture and Performance
- Uses no code from other browsers (blink, webkit, gecko)
- Built on libraries from Serenity OS project with "write everything from scratch" culture
- Uses native platform rendering: AppKit on macOS, Skia painter for GPU acceleration
- Custom JavaScript engine called LibJS
- More compatible with web standards than V8 (higher test262 scores)
- No JIT compilation - significantly slower performance
- Prime number benchmark: 1.48 seconds vs 0.47 seconds in Node/Bun
- Media playback uses FFmpeg directly
- Rendering performance issues: high CPU usage, poor scrolling, layout bugs
Browser Engine Philosophy and Goals
- Primary goal: build new browser engine from scratch to prove web standards can be implemented independently
- Concern about Google's advertising empire driving web standards
- Fear that Chrome dominance (Edge, Brave, Arc, Opera all use Chromium) creates single point of failure
- Firefox and Safari both receive significant funding from Google
- Vertical slice development approach - focus on getting specific sites working end-to-end
- Defer performance optimization until correctness/compatibility achieved
Technical Implementation Challenges
- Currently crashes frequently, poor CSS/flexbox support
- No SVG rendering, misaligned form elements
- Heavy sites like Twitch barely functional
- GitHub works but with significant layout issues
- Inspector tool extremely slow
- Font loading issues
Project Scope Evolution
- Originally part of Serenity OS "not invented here" philosophy
- Forked from Serenity to allow third-party dependencies
- Still maintaining custom JavaScript engine despite relaxed dependency policy
- Focus shifted from "new browser" to "new browser engine" with UI as secondary concern
Criticism and Alternative Approaches
- Concern about reinventing everything simultaneously makes debugging difficult
- Comparison to failed "rewrite everything" projects
- Alternative suggested: incremental replacement of Chrome components
- Question whether independence for sake of independence is worthwhile goal
- Performance vs principles tradeoff - slower but more compatible than established engines
Market Position and Viability
- Not targeting mainstream browser usage
- Goal to be "standards browser" proving web isn't Google-owned
- Comparison to Firefox's historical role in browser ecosystem
- Unlikely to gain significant user adoption but could influence standards development
- Different approach than Arc (UI innovation) vs Ladybird (engine independence)
