<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/this-month-in-ladybird-b0t2tkeh3" -->

---
title: This Month in Ladybird | daily.dev
description: August brought Ladybird video playback on Twitch and more YouTube formats via fragmented MP4 support, CSS scroll snap, JavaScript debugging in DevTools,...
canonical: https://daily.dev/posts/this-month-in-ladybird-b0t2tkeh3
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: This Month in Ladybird | daily.dev
og:description: August brought Ladybird video playback on Twitch and more YouTube formats via fragmented MP4 support, CSS scroll snap, JavaScript debugging in DevTools,...
og:url: https://daily.dev/posts/this-month-in-ladybird-b0t2tkeh3
og:image: https://api.daily.dev/og/posts/b0T2tKEH3.png
og:image:alt: This Month in Ladybird
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# This Month in Ladybird

**[Ladybird Browser](https://daily.dev/sources/ladybird)** · 15 min read · 5 upvotes · 0 comments

## Summary

August brought Ladybird video playback on Twitch and more YouTube formats via fragmented MP4 support, CSS scroll snap, JavaScript debugging in DevTools, pausable/resumable downloads, and full session restore. The bigger story is a sustained performance push: a new style engine using incremental invalidation, cached layout results, and CSS animations moved off the main thread, pushing Speedometer 2 from ~47 to ~64 and StyleBench from ~3.5 to ~83. Security work extended memory caging to the JavaScript heap, CSS parsing and the painting pipeline moved to Rust, and numerous site-compatibility fixes landed for chatgpt.com, vscode.dev, discord.com, icloud.com, strava.com, and others. WPT scores rose by 9,657 subtests, driven largely by referrer-policy tests passing.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://ladybird.org/newsletter/2026-08-31>

## Questions this post answers

### What changed in Ladybird's style engine to improve CSS performance?

Ladybird replaced its selector matching, style invalidation, cascade, and computed-style retention with a new incremental engine that treats DOM mutations, state changes, and CSSOM edits as typed deltas routed only to dependent selectors, rather than re-evaluating everything a change might affect. This pushed its StyleBench score from about 3.5 to about 83 in one month, putting it in range of major browser engines.

_Track how Ladybird's engine rewrites reshape browser performance benchmarks on daily.dev._

### Is Ladybird's rendering engine written in Rust or C++?

Ladybird is actively migrating LibWeb from C++ to Rust. As of August, CSS parsing, computed style storage and computation, and the entire painting pipeline (including display list recording and hit testing) moved fully to Rust, with old C++ paintable objects deleted. Strings now share a single representation between the two languages to avoid copying across the boundary.

_Follow Ladybird's C++ to Rust migration progress alongside other systems projects on daily.dev._

### How does Ladybird mitigate JavaScript engine memory corruption vulnerabilities?

Ladybird added a heap cage for the JavaScript engine: all garbage-collector heap blocks now live in a single reserved region, with cell payloads stored as offsets masked on decode, so a corrupted value can only address memory inside that region. Freshly generated bytecode is also stored in read-only mappings to prevent heap corruption from rewriting instruction streams.

_Keep up with browser exploit-mitigation techniques like heap caging on daily.dev._

## Community take

How the wider developer community reacted, aggregated from 2 discussions and 168 comments across lobsters, hackernews (as of 2026-09-13).

**TL;DR:** Technical excitement about Ladybird's performance and compatibility progress is heavily overshadowed by two contentious side-debates: the project's decision to close outside contributions, and character attacks on the lead developer tied to a 'fashware'/'weird guys of FOSS' list and past pronoun/political controversies.

**Sentiment:** 30% positive · 25% mixed · 45% skeptical

**The case for**

- Several people report the pre-alpha already renders heavy, modern JS/CSS/SVG apps correctly, if a bit slowly.
- The steady progress and monthly cadence of updates is seen as impressive for such an ambitious from-scratch engine effort.
- Some argue a niche browser becoming mainstream isn't unprecedented, citing KHTML's path to WebKit/Chrome.
- A few say they'd happily trade some site-compatibility gaps for a lighter, more user-focused browser.

**The pushback**

- Many are skeptical Ladybird can ever close the last 3-5% compatibility gap that separates a usable browser from a great one, comparing it to Wine/ReactOS versus Windows.
- The decision to stop accepting public pull requests and restrict contributions to a closed maintainer group is viewed by several as a disappointing retreat from the 'open, independent browser' narrative.
- Some question the entire premise of building a new engine rather than investing that effort into de-Googling or improving Firefox.
- A vocal contingent brings up personal/political criticisms of the lead developer (pronoun handling, sponsor scandals, praise of controversial figures) as reasons to distrust or boycott the project.
- Others push back hard on those criticisms as vague 'vague-shaming', mental gymnastics, or an unhealthy 'ideological trial' pattern.

**By community**

- lobsters (heated): Discussion is dominated by a long, contentious argument over a 'fashware'/'weird guys of FOSS' list naming the lead developer, with technical comments about performance and closed contributions largely sidelined.
- hackernews (mixed): Genuine technical optimism and admiration for the engineering effort coexists with skepticism about ever closing the compatibility gap, frustration over the closed-contribution model, and a smaller thread of personal criticism of the lead developer.

**Hottest debate:** Whether concerns about the lead developer's political/personal conduct are legitimate grounds for judging the project, versus dismissing them as unfounded character attacks.

**Open questions**

- Can Ladybird realistically close the last 3-5% compatibility gap that distinguishes a fully usable browser from a merely functional one?
- Will the closed-contribution model hold up long-term, or will it eventually open up or get forked if it stalls community growth?
- How much is AI assistance actually accelerating development, and is that sustainable for fixing the long tail of site-compatibility bugs?

**Highlights**

> I got asked in chat to reply here, so I'm dropping in to connect back my reasoning + better explain a decision. I left up the Stallman report for [this reasoning](https://lobste.rs/c/ser2e6); which I [referenced recently](https://lobste.rs/c/rxnmgf) and [expanded on a little here](https://lobste.rs/c/3gi2kd). I removed your comment and [banned the domain](https://lobste.rs/domains/dmpwn.info) for that reply site about DDV because the site was long on innuendo and short on evidence in a way that strongly reminds me of some particular trolls who like to make up really heinous accusations about individuals. I don't think I've done that before or since, it really was that one source was screamingly bad to me. It's not a problem that you're making this criticism, and a good citation is appreciated. FWIW, DeVault has also [confirmed his involvement](https://drewdevault.com/blog/Addressing-harassment/#:~:text=I%20was%20involved%20in%20editing%20The%20Stallman%20Report).
> — [pushcx on lobsters · 3 points](https://lobste.rs/s/npyzwy/this_month_ladybird_august_2026#c_1vds3k)

> You should probably link receipts if you see fit to post a comment like this. I don't mean to diminish the validity of your concerns, at all. If I knew what you were talking about, we would likely agree! But this kind of vague-shaming someone is really rough, and doesn't give us anything to latch onto about this list or what would make someone suited to maintain such a list. Also, Drew linked receipts in much of his commentary.
> — [hoistbypetard on lobsters · 6 points, 1 comments](https://lobste.rs/s/npyzwy/this_month_ladybird_august_2026#c_kygwlu)

> > 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?
> — [sho\_hn on hackernews · 7 comments](https://news.ycombinator.com/item?id=49602531)

> 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-...
> — [senfiaj on hackernews · 9 comments](https://news.ycombinator.com/item?id=49604124)

> > It's impressive that they're doing such titanic work. I think it is still a bit too early to say that. The most difficult part is to ensure the security of the implementation, and not just the checkbox compliance against standards. So when this survives the swarm of pentesters, it will be a absolute titanic work. Otherwise it might be too risky to use.
> — [nicce on hackernews](https://news.ycombinator.com/item?id=49609789)

**Source threads**

- [lobsters](https://lobste.rs/s/npyzwy/this_month_ladybird_august_2026) · 22 points · 37 comments
- [hackernews](https://news.ycombinator.com/item?id=49571096) · 215 points · 131 comments

## Similar posts on daily.dev

- [This Month in Ladybird](https://daily.dev/posts/this-month-in-ladybird-wmtgqhzgv) · Hacker News · 12 upvotes · 2 comments

---

Tags: [#css](https://daily.dev/tags/css), [#rust](https://daily.dev/tags/rust), [#browsers](https://daily.dev/tags/browsers)

[View this post on daily.dev](https://daily.dev/posts/this-month-in-ladybird-b0t2tkeh3)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"This Month in Ladybird","url":"https://daily.dev/posts/this-month-in-ladybird-b0t2tkeh3","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/this-month-in-ladybird-b0t2tkeh3"},"datePublished":"2026-09-04T16:48:20.739Z","dateModified":"2026-09-13T20:48:50.484Z","description":"August brought Ladybird video playback on Twitch and more YouTube formats via fragmented MP4 support, CSS scroll snap, JavaScript debugging in DevTools,...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/f0d04d597be9efdaf11883698ad30378?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/f0d04d597be9efdaf11883698ad30378?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Ladybird Browser","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Ladybird Browser","logo":"https://media.daily.dev/image/upload/s--gBOjamNh--/f_auto,q_auto/v1788155675/logos/ladybird?_a=BAMAMicg0","url":"https://daily.dev/sources/ladybird"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/this-month-in-ladybird-b0t2tkeh3","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":5},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"css,rust,browsers","timeRequired":"PT15M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Ladybird Browser","item":"https://daily.dev/sources/ladybird"},{"@type":"ListItem","position":3,"name":"This Month in Ladybird"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/this-month-in-ladybird-b0t2tkeh3#faq","mainEntity":[{"@type":"Question","name":"What changed in Ladybird's style engine to improve CSS performance?","acceptedAnswer":{"@type":"Answer","text":"Ladybird replaced its selector matching, style invalidation, cascade, and computed-style retention with a new incremental engine that treats DOM mutations, state changes, and CSSOM edits as typed deltas routed only to dependent selectors, rather than re-evaluating everything a change might affect. This pushed its StyleBench score from about 3.5 to about 83 in one month, putting it in range of major browser engines. Track how Ladybird's engine rewrites reshape browser performance benchmarks on daily.dev."}},{"@type":"Question","name":"Is Ladybird's rendering engine written in Rust or C++?","acceptedAnswer":{"@type":"Answer","text":"Ladybird is actively migrating LibWeb from C++ to Rust. As of August, CSS parsing, computed style storage and computation, and the entire painting pipeline (including display list recording and hit testing) moved fully to Rust, with old C++ paintable objects deleted. Strings now share a single representation between the two languages to avoid copying across the boundary. Follow Ladybird's C++ to Rust migration progress alongside other systems projects on daily.dev."}},{"@type":"Question","name":"How does Ladybird mitigate JavaScript engine memory corruption vulnerabilities?","acceptedAnswer":{"@type":"Answer","text":"Ladybird added a heap cage for the JavaScript engine: all garbage-collector heap blocks now live in a single reserved region, with cell payloads stored as offsets masked on decode, so a corrupted value can only address memory inside that region. Freshly generated bytecode is also stored in read-only mappings to prevent heap corruption from rewriting instruction streams. Keep up with browser exploit-mitigation techniques like heap caging on daily.dev."}}]}
```

