This Month in Ladybird – August 2026
ladybird.org153 points by exploraz 3 days ago
153 points by exploraz 3 days ago
I am watching this project with interest.
It's impressive that they're doing such titanic work. However, I'm highly skeptical that they can create a real rival to established browsers. I'm sorry for telling this, but Web standards are simply too complex and huge. Ladybird to Chrome / Firefox is almost like Wine / ReactOS to Windows, that last 3-5% of gap actually differentiates a normal browser from a browser that is a pain for web developers. And it's the most stubborn part to be fixed. Also, keep in mind that it hasn't much market, at least IE had a significant market that forced the developers to support it (with all the hate).
https://waspdev.com/articles/2025-04-07/will-there-be-a-new-...
As of a week ago their pre-alpha version was capable of running my extremely heavy JS+ SVG + worker thread + SSE app, a bit slowly I admit but correctly in all major exercises I tried. So, I'm optimistic. They're doing great.
Separately I wonder if the compatibility job is easier now that you can just give the HTML5 spec to Fable and Bob's your uncle.
The browser might reach to 95-97% compatibility eventually. But the last 3-5% gaps are the most stubborn. Many of these 3-5% are not trivial API calls. They might be some subtle legacy quirks, timing/rendering things, etc. There is a lot of poorly written historical code that might be illegal by web standards but browsers are forced to support. Established browsers have decades of patches and regression testing.
The history of Chrome and Safari traces back to KTML, the renderer for Konqueror, a niche browser on Linux with so little market share there weren't real conversations about it ever seriously competing with Firefox or IE.
Then something unexpected happened: Apple adopted KHTML for Safari's WebKit. WebKit was then adopted as the render for Chrome
Could a niche browser still become mainstream /today/? I think so.
The web standards are enormously complex compared to that time. Not sure if today's tooling can compensate this.
I didn't expect to see Twitch working so soon!
Ladybird seems to have received a nice boost in momentum in the past two years. If you've ever watched one of Andreas videos on YouTube you'll find he's incredibly driven and knowledgeable in this area. I can imagine someone like him would go from being a "10x programmer" to a "100x programmer" with AI assistance. I am not entirely sure to what degree AI is being leveraged to speed up development, but I am indeed happier I might be able to ditch FF and begin using their browser soon.
> Ladybird seems to have received a nice boost in momentum in the past two years.
I'm still very interested in the project and look forward to each monthly update, and I can empathize (though not agree) with the reasoning, but something is off ever since they announced the decision to close the project to outside contributions. It's still Open Source, but only a self-selected group of maintainers gets to write and merge code, at least for the time being.
Somehow that's not the "a new independent Open Source browser" future I thought we had signed up for with our attention.
Again, I understand all the arguments for why at this particular time they feel that they cannot afford the energy expense required need to run a community. First-hand, actually, because I am involved with running a very large one myself.
But it makes me think a lot about the value proposition of the product. Re-creating Firefox/Chrome can still be a useful exercise, but from an end-user POV another exchangable web browser will not rock their world. Wouldn't the real product be healthy governance?
The flood of low effort AI-contributions makes accepting anonymous contributions impractical nowadays. They'd waste hours reviewing things of no value. I know because it happened to several of my moderately successful projects. At some point I had to stop caring. I now only review the PR if the message is a single unformatted paragraph with few emojis, I find this to be a good signal that it was made by a human and not an agent (the code could still be LLM but a human cared enough to write their own message). I'm sure I will miss genuinely good and valuable contributions, but the signal-to-noise ratio is just too low.
It would be 100x worse for them because who wouldn't want to have a browser in their contribution portfolio when seeking a job?
A lot of folks might not want to hear it, but realistically some there's going to have to be a cultural realization that machine-generated low effort slop is not any more desired or helpful than human-generated low effort slop.
That's not an outright rejection of LLM-assisted code, it just means that a real person needs to be awake, at the wheel, and just as significant of a contributor. Literally anybody can point Claude at a repo and say "add X feature" or "fix Y bug" and so PRs that do that carry no value.
The value of a feature or a bugfix is not calculated from the effort required but from the need or desire for said feature or bugfix. So whether or not the barrier to entry has been lowered by llm's is irrelevant. What matters as to it's value is the result.
The important part is the quality of the code, how well-considered its design is, how well it gels with existing code, how readable it is to other humans, how well documented it is, how well its author understands it (and thus, can make surgical changes if needed), and how well it was tested.
A PR that implements a sought out feature or bug fix can be practically worthless if it doesn’t check some percentage of those boxes. The line differs per project naturally, but almost nobody wants a PR that is missing all of them.
OK, boomer.
but seriously I do wonder whether our conservative pull to keep control over our code is going to survive even the next 6 months.
Free and open-source software licenses never promised that any given project would absolutely accept code contributions from the general public. You're as free to exercise the Four Freedoms with Ladybird as you are with Firefox or Chromium, including the freedom to fork it; and your practical ability to get your own change merged into upstream Ladybird is probably about as good as it is for Firefox/Chromium, too.
I agree with your concerns but also think that a new viable browser engine will be such a benefit to the health of the open web that I'm willing to overlook such irregularities, at least for now. sqlite doesn't accept contributions either and it's done well for itself, and if Ladybird ends up going sour there's always the possibility of a fork. This is similar to my stance towards Firefox: despite the actions of Mozilla Corp, having at least one non-Blink engine is too important, and for friends and family that I care about, working ad-blockers are essential so there's no practical alternative.
> Again, I understand all the arguments for why at this particular time they feel that they cannot afford the energy expense required need to run a community. First-hand, actually, because I am involved with running a very large one myself.
This is a problem brought on by AI, and does not seem fair to imply it's Ladybird's problem to solve.
Writing a browser/engine from scratch is a massively ambitious undertaking by itself. I don't expect them to also solve the tangential AI problem that every other open source project is contending with. Others can step up for that one.
Said announcement: https://ladybird.org/posts/changing-how-we-develop-ladybird/
> It's still Open Source, but only a self-selected group of maintainers gets to write and merge code, at least for the time being.
That is the way the BSDs are developed and they're free software. If you want to you can pull the code and modify whatever you want. Let them get the thing up and running first, then see how the project handles external contributions. If they somehow fail to see the brilliance of some external contribution a fork will soon take over from where they dug themselves in, something which has happened many times over in free software land: Firefox (took over from the Mozilla Suite), Libreoffice (took over from Openoffice), Nextcloud (took over from Owncloud), egcs (took over from gcc, later became the main gcc branch), etc.
Don't BSDs accept new contributors and patches tho? A long time ago I worked in the freebsd documentation project (translating th handbook) and it was pretty easy to join the core group. And ooenbsd pioneered anoncvs didn't it?
For ladybird it seems the group is closed to outsiders.
Linux had an existing population of Unix engineers who had a strong incentive to build something that could replace the Unix systems they were paying for.
Ladybird doesn’t replace something developers are already paying for, so the incentive to make substantial, high-quality contributions is much weaker.
Really excited for alpha. When it hits I plan on using it for my daily driver to help them with usage stats and crash reports.
> We also download over four parallel connections where possible.
I hope you can turn that off. It fragments the file and puts unnecessary load on the server.
You never used a download manager like DownThemAll or GetBot back in the day?
As far as fragmentation goes, I think both Firefox and Chrome derivatives figure out the final file size in advance, pre-allocate a temporary file that long and put data in it as it arrives. Completing the download is a rename operation or a no-op.
GetRight was a fucking lifesaver when I was stuck on a 28.8k dial up connection that loved to drop at the worst possible time.
> unnecessary load
In some situations it's the only way to get a decent download speed.
This is such a nerdy newsletter I love it
Are there other sites that get through ad blockers as well as Twitch?
Feels like the old "browser wars" days again. Between AI productivity, and Google losing the grace to bloat the web specs, I wouldn't be surprised if it starts to take market share away from other browsers as soon as it's stable.
Sure, it could easily take 1%.
Going above 5%, OTOH, I would be shocked to ever see happen, for two reasons. 1) Mass-market adoption requires working well on an enormous long tail, which is difficult without a large team. 2) The primary driver of playing at that size is mass marketing/distribution, which requires $$$. Engineering a great product is necessary, but not sufficient.
My perspective on this is informed by being on Google Chrome from inception to 2025. Chrome from near the beginning was well-engineered and had three compelling-according-to-user-research advantages over the IE of 2008 (speed, security, and not being made by Microsoft), but mass adoption depended on a large number of non-engineering factors, of which marketing/distribution was (to a then-mid-20s software engineer) the most surprising one. I didn't believe that was what made the difference in which browser most people used; I was very wrong. Techies are not the leading-edge trendsetters for the masses we sometimes believe we are.
IMO, taking mass market share in the future will require either a compelling-to-users product coupled with at least a couple hundred million dollars in marketing and distribution budget, or else something that is completely unlike web browsers of the past (maybe there's something that replaces the web entirely). No one has done the former since Chrome launched; the closest people have come to the latter thus far is things like Dia/Atlas that try to reimagine workflows in an AI context, and I think the market has not found those to be sufficiently different+compelling.
Yeah basically everybody I know who's non-technical switched to Chrome when Google started advertising it on google.com (This was back when nontechnical users would start every search query by going to google.com). "Oh this says it's better and faster, let me download it". Google also paid shareware/freeware developers to bundle Chrome with their installers if you didn't uncheck some option in the "expert install" mode. Chrome would then launch and prompt the user to set it as the default browser. This is somewhat questionable, but this sort of developer usually pushes some sort of malware in their installers so I suppose Chrome was an improvement on that.
The distribution opt-outs really bugged me at the time, and I went and talked to the marketing team. Surprisingly, users who got Chrome via one of those opt-out deals used it at rates/in ways statistically indistinguishable from "organic" users (i.e. users who manually downloaded Chrome and installed it). This was a pretty strong counterargument to the idea that we were pushing something unhelpful on people who didn't want it -- they seemed to "want it" as much as the people who'd bothered to go find it manually.
I still didn't (and don't) love the practice, but it called in to question a lot of my assumptions about what people knew about software, why they used what they did, how they found it, etc.
I agree, 1% is reasonable. That's still a huge number of people. And, not all users are created equal. If that 1% of everyone is skewed towards the more educated, IE if 5% of millionaires switch, that's 5% fewer eyeballs looking at a sports car ad.
lol this is such a funny scam. these investors are so easy to fool
what makes this a scam in your opinion, and how exactly do you reckon they are fooling investors?
snide vagueposting is a lot less cool than you think it is