Ladybird Browser Adopts Rust to Replace C++ with AI Help

Ladybird's own blog post titled "Ladybird adopts Rust, with help from AI" on 2026-02-23 announces the project will adopt Rust as its successor to C++ for memory safety, and credits AI-assisted translation in the work led by Andreas Kling. The post follows a run of monthly updates through 2025 and January 2026 that covered site compatibility, Gmail performance, painting architecture, IPC hardening, HTTP caching, and media streaming.

Kling and the team targeted LibJS, Ladybird's JavaScript engine frontend, as the first port because its stages are self-contained and well tested. As Simon Willison quoted from Kling: "Our first target was LibJS, Ladybird's JavaScript engine. The lexer, parser, AST, and bytecode generator are relatively self-contained and have extensive test coverage through test262, which made them a natural starting point."

Kling described the translation workflow in technical detail on Hacker News: "I used Claude Code and Codex for the translation. This was human-directed, not autonomous code generation. I decided what to port, in what order, and what the Rust code should look like. It was hundreds of small prompts, steering the agents where things needed to go. After the initial translation, I ran multiple passes of adversarial review, asking different models to analyze the code for mistakes and bad patterns." He also stressed a tight verification bar: "The requirement from the start was byte-for-byte identical output from both pipelines." Kling reported "about 25,000 lines of Rust," though the Hacker News excerpt omits a confirmed total elapsed time; an Original Report claims "They ported JS engine frontend to Rust in 2 weeks using AI," a duration that remains unconfirmed by Kling's quoted notes.

Operationally, Ladybird is treating Rust work as a parallel effort rather than an immediate drop-in replacement for existing C++ development. The Register reported the project "blames a delay in its development of around a year on its attempts to use Apple's Swift programming language," adds that a GitHub issue "says that's history," and states "For now, work continues in C++, with a side project porting subsystems to Rust running in parallel."

Reaction in developer communities has been immediate and mixed. Hacker News registered a hot thread with 163 points and dozens of comments, while Lobste.rs archived at least 19 comments. Lobste.rs commenter tuananh praised the approach: "zero regression is pretty cool. it's nice to have a comprehensive test suite." Other Lobste.rs posts raised reputational concerns about the project's founder, with jussi writing "Cool, too bad Ladybird is riddled with controversies (founder supporting the white replacement theory and fascism) :/," prompting a back-and-forth in the thread.

For Rust and browser-engine developers evaluating AI-assisted ports, the concrete artifacts Kling lists matter: test262-driven conformance, byte-for-byte output comparison between C++ and Rust pipelines, use of Claude Code and Codex, adversarial multi-model review, and the roughly 25,000-line Rust result attributed to the LibJS frontend. Open technical questions remain: confirm whether the 25,000-line count covers only the LibJS frontend, verify the Original Report's "2 weeks" elapsed-time claim, and clarify the long-term scope of "adopting Rust" beyond parallel subsystem ports. Ladybird's February 23, 2026 announcement provides a reproducible case study for teams considering Rust and LLM-assisted translation, but the project still lists ongoing C++ work and a staged migration path.