Ladybird Browser adopts Rust

Re:Ladybird Browser adopts Rust by bee_rider on Monday February 23, 2026 @11:23AM (#47124461)

I haven’t done a ton of porting. And when I did, it was more like a reimplementation.

> We’ve verified that every AST produced by the Rust parser is identical to the C++ one, and all bytecode generated by the Rust compiler is identical to the C++ compiler’s output.

Is this a conventional goal? It seems like quite an achievement.

[ Parent | on HN ]

Re:Ladybird Browser adopts Rust by tinco on Monday February 23, 2026 @12:20PM (#47125376)

My company helps companies do migrations using LLM agents and rigid validations, and it is not a surprising goal. Of course most projects are not as clean as a compiler is in terms of their inputs and outputs, but our pitch to customers is that we aim to do bug-for-bug compatible migrations.

Porting a project from PHP7 to PHP8, you'd want the exact same SQL statements to be sent to the server for your test suite, or at least be able to explain the differences. Porting AngularJS to Vue, you'd want the same backend requests, etc..

[ Parent | on HN ]

Re:Ladybird Browser adopts Rust by adw on Monday February 23, 2026 @12:29PM (#47125520)

It’s a very good way of getting LLMs to work autonomously for a long time; give it a spec and a complete test suite, shut the door; and ask it to call you when all the tests pass.

[ Parent | on HN ]