Ladybird has been really shaping up over the last month or so, I pull and build the latest bits every morning and use it for low stakes web browsing (HN, news sites, reddit, youtube, blogs, etc.) and it's getting very close to the point where I forget that it's a pre-alpha.
Very exciting to watch a completely new browser/browser engine come together. Reminds me of the early days of Mozilla and Gecko
It was about time. BTW, when this gem uses EGui instead of QT6 (nothing against QT, but once everything uses Rust, it will be no reason to keep it) it will shine.
Would love to see where all the folks from 5 years ago, breathlessly declaring it's futile to start a new browser project, are now and what they are doing with their lives.
Honest question for people. I'm a C++ dev and I'm seeing a lot of moves to rust. Everyone is using agents to move stuff to rust and I tried it myself. The amount of insane hardrive space usage (over 90GB of build artifacts that constantly need cleanup) is that normal? What am I doing wrong. Are people seeing advantages after a move to rust that wasn't there in C++ (assuming no new features). Like is your project better after moving to rust in obvious ways?
It's expected. Cargo has very conservative cache cleanup (once per month IIRC).
There's incremental compilation cache that generates lots of churn (although Rust's compilation unit is a crate, "queries" in the compiler are cached individually, creating many cache entries per function per type).
The other half of the disk space is debug info, because abstractions that optimize down to zero runtime code still carry all of their source-level debug info.
These can be adjusted in build profiles if you're ok with coarser debug info or less fine-grained caching.
Very exciting to watch a completely new browser/browser engine come together. Reminds me of the early days of Mozilla and Gecko
Posted with Ladybird :)
It was about time. BTW, when this gem uses EGui instead of QT6 (nothing against QT, but once everything uses Rust, it will be no reason to keep it) it will shine.
https://github.com/LadybirdBrowser/ladybird/blob/master/Docu...
There's incremental compilation cache that generates lots of churn (although Rust's compilation unit is a crate, "queries" in the compiler are cached individually, creating many cache entries per function per type).
The other half of the disk space is debug info, because abstractions that optimize down to zero runtime code still carry all of their source-level debug info.
These can be adjusted in build profiles if you're ok with coarser debug info or less fine-grained caching.
https://blog.rust-lang.org/inside-rust/2026/08/18/reducing-t...
but i still love rust ofc
When I mentioned, after C++26 failed its vote, that maybe they should use this extra time to focus more on memory safety, I got downvoted instead.
Surely that attitude isn't helping their situation.