News for hackers. Stuff that matters.
Re:Changing How We Develop Ladybird by Deukhoofd on Friday June 05, 2026 @04:36AM (#48409703)
This rather feels like it's completely stepping away from the thing that made the community around Serenity and Ladybird so good.
Re:Changing How We Develop Ladybird by coldtea on Friday June 05, 2026 @07:33AM (#48410999)
What made the community so good, is that it was a community.

Any rando armed with an LLM is not a community.

Re:Changing How We Develop Ladybird by rjh29 on Friday June 05, 2026 @06:08AM (#48410365)
I'd argue that was what made Serenity good - a toy OS that anyone can code anything for. Want to spend ages working on a painting program? Make screensavers? Add drivers for your printer? Port Doom? Improve font support because it sounds fun? etc. It celebrated coding for coding's sake, which is the antithesis of AI. There's no point vibe coding features for Serenity because there is no real product there.

On the other hand, Ladybird is gearing up to become a production-ready browser for real users. Adding fun features for the sake of it, and hand-rolling code to parse PNGs and the like, has become a liability for the project.

Re:Changing How We Develop Ladybird by conaclos on Friday June 05, 2026 @05:07AM (#48409925)
I lost all trust in the project since the LLM rewrite. This new step is another red flag to me.
Re:Changing How We Develop Ladybird by siwatanejo on Friday June 05, 2026 @05:25AM (#48410074)
what rewrite? I thought it would switch to Rust but I still see it to be C++
Re:Changing How We Develop Ladybird by afdbcreid on Friday June 05, 2026 @06:19AM (#48410423)
They are adopting Rust (https://ladybird.org/posts/adopting-rust/) and use LLMs to help with the rewrite, but not all code was migrated yet. Also it's definitely not a big-bang-rewrite-the-world-with-Claude like Bun.