Ladybird Web Browser becomes a non-profit with $1M from GitHub Founder
Ladybird Web Browser, now "The Ladybird Browser Initiative," shifts to a non-profit model led by Andreas Kling and Chris Wanstrath. It aims for a corporate-free, user-focused browser funded by donations and sponsorships. Wanstrath pledged $1 million, targeting an alpha release in 2026.
Read original articleLadybird Web Browser, founded by Andreas Kling and supported by GitHub founder Chris Wanstrath, is transitioning into a non-profit organization called "The Ladybird Browser Initiative." The initiative aims to develop a new web browser from scratch without relying on corporate funding or advertising revenue. Ladybird has received significant financial support, including a $1 million pledge from Wanstrath. The browser's development progress is promising, with plans to release an alpha version by 2026. Ladybird's unique approach involves funding solely through sponsorships and donations, ensuring independence from corporate influence. The initiative emphasizes a commitment to open standards and user privacy, distinguishing itself from major browsers funded by advertising giants like Google. Ladybird's focus on building a browser free from corporate control and advertising aligns with its mission to prioritize user interests and contribute to a diverse web ecosystem. Despite facing challenges in the competitive browser market, Ladybird's community-driven development and dedication to a transparent, non-commercial model offer a refreshing alternative for users seeking an independent browsing experience.
Related
Ladybird browser update (June 2024) [video]
The Ladybird browser project, a spin-off from Serenity OS, now focuses on browser functionality. Managed by maintainers, it integrates third-party libraries, HTTP cache, Shadow DOM, and web APIs. Ongoing developments aim to improve validation, caching, JavaScript, WebAssembly, find, and page features, enhancing user experience.
Ladybird Announcement [video]
Chris Wroth, GitHub co-founder, and Andreas Cling collaborate on Ladybird Browser Initiative, creating an indie games publisher and game platform with an open-source browser engine. Wroth invests $1 million, seeking community support for the distinctive browsing experience.
Welcome to Ladybird
Ladybird is a non-profit web browser project aiming for modern browsing with performance and security. Developed independently, it targets Linux and macOS, funded by sponsorships and donations, welcoming community contributions.
The Ladybird Browser Initiative
The Ladybird Browser Initiative, launched on July 1st, 2024, introduces an independent, open-source browser with a new engine based on web standards. Supported on Linux and macOS, it aims to become a fast, stable, privacy-focused browser funded by sponsorships and donations. Led by Andreas Kling and Chris Wanstrath, the project focuses on community contributions for continuous improvement.
Welcome to Ladybird, a truly independent web browser
Ladybird is an independent web browser project prioritizing performance, stability, and security. It's developed from scratch, adheres to web standards, and plans an Alpha release in 2026 for Linux, macOS, and Unix-like systems. Funding comes from sponsorships and donations, with no user monetization. Developers can contribute via GitHub and Discord. The team includes paid engineers and volunteers, with potential expansion. Future plans may involve Windows and mobile support, exploring languages beyond C++. Sponsorships are unrestricted to maintain project independence.
Here's a short video from Chris Wanstrath announcing our non-profit yesterday, and kicking things off with a $1M donation: https://www.youtube.com/watch?v=k9edTqPMX_k
Happy to answer questions :)
>Ladybird started as a component of the SerenityOS hobby project, which only allows C++. The choice of language was not so much a technical decision, but more one of personal convenience. Andreas was most comfortable with C++ when creating SerenityOS, and now we have almost half a million lines of modern C++ to maintain.
>However, now that Ladybird has forked and become its own independent project, all constraints previously imposed by SerenityOS are no longer in effect. We are actively evaluating a number of alternatives and will be adding a mature successor language to the project in the near future. This process is already quite far along, and prototypes exist in multiple languages.
https://assets.mozilla.net/annualreport/2022/mozilla-fdn-202...
I want ladybird to succeed and show the world how ridiculous the Mozilla situation has been.
I quickly put together a "cleaner" design for anyone interested, which also uses the original (and objectively better) logo:
P.S. Check out my UI/UX portfolio at https://hipfolio.co
This of course comes at the cost of not being able to support non-free parts of the web standard such as DRM.
I am happy to see the project thrive.
I hope that as Ladybird grows you'll keep privacy, security, and customization in mind because our options in that space are very limited.
It would be a statement of hope that we are not condemned to Google’s corporate strategy and the absolute rot the Mozilla foundation has become.
I know pretty much everything is not in their favor but I truly believe it’s still possible for a couple of guys with their head between their shoulders to actually “change the World”. I need to sleep at night after all.
I loved opera to death in the early 2000s. I was young and broke and didn't want to pay for it, but even though there were cracked versions around I dealt with the officially free, ad-sponsored version (Google ads, ironically) because I wanted to support it.
Now I've donated to Firefox in the past, but they've disappointed again and again with questionable business decisions. Still, I'm exclusively using Firefox than anything Chromium-based out of principle and I think I will switch to ladybird as soon as feasible. I have no problem paying for a browser that's truly independent.
Meanwhile Mozilla spends a massive chunk of money on the organization and the philanthropy and the blog posts, and the activism, and the salaries of people who have little resemblance to engineers.
This also makes me a bit of a tab hoarder, though.
I'd say "I'll be keeping an eye on this," but I'm sure there'll be plenty of posts about Ladybird before the alpha even drops, haha.
I can't wait to see the absolute mountain of perfect pull requests all these people bring to the project!
Seriously though, congratulations Andreas and please keep the faith. We might not be the loudest voices, but almost all of us are cheering for you.
Sounds good, but how would you make sure the sponsors won’t influence you in the future once it’s popular enough? After all, they are still corporations and are after profits, as opposed to crowdfunding.
Is this going to work with screen readers, magnification, speech recognition etc? I guess a more abstract version of that question is: Does Ladybird intend to offer some kind of feature parity with existing solutions where integration with OS-specific accessibility architectures (UIA, AT-SPI2, etc.) are concerned? If not, it's a non-starter for quite a few people, and I'd rather know so I know to even keep up with this project or add it to the "user first but oh not actually all users first" pile :)
I work at Brave, VP of IT. I worked at Mozilla for 5 years. So have some experience with browsers.
I see our insanely high infrastructure bill each month, most of the cost comes down to CDN/distribution of updates, block lists, safe browsing etc. But we also have a bunch of other costs for staff to maintain said infrastructure and security.
If you get to scale, what is the plan here? Because $1M won't get you a very long runway and the moment browsers stop doing what they should be doing well, they die. Wishing you the best of luck.
Even LGPLv3+ would be a good choice here.
> At the moment, many core library support components are inherited from SerenityOS:
LibWeb: Web rendering engine LibJS: JavaScript engine LibWasm: WebAssembly implementation LibCrypto/LibTLS: Cryptography primitives and Transport Layer Security LibHTTP: HTTP/1.1 client LibGfx: 2D Graphics Library, Image Decoding and Rendering LibArchive: Archive file format support LibUnicode: Unicode and locale support LibAudio, LibMedia: Audio and video playback LibCore: Event loop, OS abstraction layer LibIPC: Inter-process communication
> Because of Brazilian government demands to remove creators from our platform, Locals is currently unavailable in Brazil
> We are challenging these government demands and hope to restore access soon
Does anyone have access to it?
Also, I am very curious why is someone like Shopify sponsoring this.
I can imagine how hard it is to develop a browser. However, I can't imagine how much the landscape will change in the next 2 years... LLM, privacy, etc.
How come a european project becomes an american foundation?
There's only one way we can make sure we can get really independent browsers:
SIMPLIFY THE WEB
- Limit the platform to absolute minimum - give way to render things, fetch stuff from the network, etc.
- Get rid of CSS - leave just some basic rendering primitives, so libraries can be created to paint on the canvas. We don't need 78 new animation primitives. We'll build them ourselves if we have a sensible canvas and execution platform.
- Move JS out of the browser to a WebAssembly compiler and make browsers run only WebAssembly
- Or keep JS in the browser but don't add any new features, features should be in libraries outside of the browser. Language should be as simple as possible.
- Get rid of all semantic html junk. We only need some basic blocks to move things around.
This way we can have simple browsers and move all complexity to client libraries, which you can pick and replace when needed. Just keep things as simple as possible and let people build on that.
(updated whitespace)
Announcement post: https://ladybird.org/announcement.html
Probably merge these discussions: https://news.ycombinator.com/item?id=40845951
Or what Firefox is doing wrong.
Or what sets this apart from existing browsers, besides the funding model.
As a end user, what should I be excited about?
As a developer, what should I be excited about?
> Ladybird is in a pre-alpha state, and only suitable for use by developers
Ironically for a story about a webbrowser, the screen is showing 404 comments as I type this. :-)
Announcement post: https://ladybird.org/announcement.html
More discussion: https://news.ycombinator.com/item?id=40845951
What an intriguing name for a web browser.
And what if you succeed? Best of luck on this bold endeavor, and try not to break our hearts.
Mmmmmmh, I don't think this is a good goal. I would expect quicker iterations even with the web browser complexities.
It would give hope we're not doomed to Google’s corporate strategy of cannibalization.
2. Would it have the features of the Line Mode Browser?
> preparing to become the only major web browser which does not treat the user like the product being sold.
...is either ignorant or a deliberate slam on Mozilla. Whatever else you might say about Firefox, it has never tried to "sell" me to anyone. The fact of the matter is that Mozilla has done the impossible for decades and gets no end of grief for it.
(I expect we'll get a zillion complaints about search engine placement & Pocket recommendations because that always happens on this site)
The risk of exploits is too high
WebGL, WebGL2, WebGPU, WebNN, WebXR, WebAudio, WebRTC, WebAssembly? Etc....?
Each of those seem like a multi-year project for a team on their own if you're not going to take code from any other browser
legacyPackages.x86_64-linux.ladybird (0-unstable-2024-06-04)
Cool! Let's see if I can read HN. nix run nixpkgs#ladybird
...
502144.831 Ladybird(1297933): WebContent process crashed!
502144.831 Ladybird(1297933): WebContent has crashed 5 times in quick succession! Not restarting...
...
I didn't expect it to work very well yet in a distro, so that's ok. It's cool enough that nix(os) has already started tracking it.I'll check back every few months and see how it's going!
good luck
- Quark is written in Coq and is formally verified. What can be learned from the design of Quark and other larger formally-verified apps.
From "Why Don't People Use Formal Methods?" (2019) https://news.ycombinator.com/item?id=18965964 :
> - "Quark : A Web Browser with a Formally Verified Kernel" (2012) (Coq, Haskell) http://goto.ucsd.edu/quark/
From https://news.ycombinator.com/item?id=37451147 :
> - "How to Discover and Prevent Linux Kernel Zero-day Exploit using Formal Verification" (2021) [w/ Coq] http://digamma.ai/blog/discover-prevent-linux-kernel-zero-da... https://news.ycombinator.com/item?id=31617335
- Rootless containers require /etc/subuids to remap uids. Browsers could run subprocesses like rootless containers in addition to namespaces and application-level sandboxing.
- Chrome and Firefox use the same pwn2own'd sandbox.
- Container-selinux and rootless containers and browser tab processes
- "Memory Sealing "Mseal" System Call Merged for Linux 6.10" (2024) https://news.ycombinator.com/item?id=40474551
- Endokernel process isolation: From "The Docker+WASM Technical Preview" https://news.ycombinator.com/item?id=33324934
- QubesOS isolates processes with VMs.
- Gvisor and Kata containers further isolate container processes
- W3C Web Worker API and W3C Service Worker API and process isolation, and resource utilization
- From "WebGPU is now available on Android" https://news.ycombinator.com/item?id=39046787 :
>> What are some ideas for UI Visual Affordances to solve for bad UX due to slow browser tabs and extensions?
>> - [ ] UBY: Browsers: Strobe the tab or extension button when it's beyond (configurable) resource usage thresholds
>> - [ ] UBY: Browsers: Vary the {color, size, fill} of the tabs according to their relative resource utilization
>> - [ ] ENH,SEC: Browsers: specify per-tab/per-domain resource quotas: CPU
- What can be learned from few methods and patterns from rust rewrites, again of larger applications
"MotorOS: a Rust-first operating system for x64 VMs" https://news.ycombinator.com/item?id=38907876 :
> "Maestro: A Linux-compatible kernel in Rust" (2023) https://news.ycombinator.com/item?id=38852360#38857185 ; redox-os, cosmic-de , Motūrus OS; MotorOS
From "Industry forms consortium to drive adoption of Rust in safety-critical systems" (2024) https://news.ycombinator.com/item?id=34743393 :
> - "The Rust Implementation of GNU Coreutils Is Becoming Remarkably Robust" https://news.ycombinator.com/item?id=34743393
> [Rust Secure Coding Guidelines, awesome-safety-critical,]
I mean it both in a sarcastic way and not.
Such soulless corpo design is not befitting of a project this nice.
Why not fork Firefox or Chromium?
Can you point to an example where Mozilla's funding model led it to make a bad decision?
Related
Ladybird browser update (June 2024) [video]
The Ladybird browser project, a spin-off from Serenity OS, now focuses on browser functionality. Managed by maintainers, it integrates third-party libraries, HTTP cache, Shadow DOM, and web APIs. Ongoing developments aim to improve validation, caching, JavaScript, WebAssembly, find, and page features, enhancing user experience.
Ladybird Announcement [video]
Chris Wroth, GitHub co-founder, and Andreas Cling collaborate on Ladybird Browser Initiative, creating an indie games publisher and game platform with an open-source browser engine. Wroth invests $1 million, seeking community support for the distinctive browsing experience.
Welcome to Ladybird
Ladybird is a non-profit web browser project aiming for modern browsing with performance and security. Developed independently, it targets Linux and macOS, funded by sponsorships and donations, welcoming community contributions.
The Ladybird Browser Initiative
The Ladybird Browser Initiative, launched on July 1st, 2024, introduces an independent, open-source browser with a new engine based on web standards. Supported on Linux and macOS, it aims to become a fast, stable, privacy-focused browser funded by sponsorships and donations. Led by Andreas Kling and Chris Wanstrath, the project focuses on community contributions for continuous improvement.
Welcome to Ladybird, a truly independent web browser
Ladybird is an independent web browser project prioritizing performance, stability, and security. It's developed from scratch, adheres to web standards, and plans an Alpha release in 2026 for Linux, macOS, and Unix-like systems. Funding comes from sponsorships and donations, with no user monetization. Developers can contribute via GitHub and Discord. The team includes paid engineers and volunteers, with potential expansion. Future plans may involve Windows and mobile support, exploring languages beyond C++. Sponsorships are unrestricted to maintain project independence.