Would also be interested to hear why. Personally I used to watch serenityOS and only recently relooked into it to see the main guy was no longer leading it but working on ladybird full time
Myself, my annoyance with Ladybird is that restarted everything from scratch. There are components of servo that are really good and basically complete. Why not use those components and concentrate on the components where you have design conflicts with Servo?
They did start with C++. They experimented with Swift, then experimented with Rust, ultimately choosing Rust. I don't see how experimenting with things makes anything "not serious". If you don't question your primitives and just accept them "because that's how it has always been", you're not a very good engineer in my book. In any case, the tech stack is not in constant flux as you claim, it's still C++, with more and more parts moving / being started in Rust, with the eventual probability of Rust replacing C++ organically, I suppose. Seems like pretty sound strategy to me to slowly, but surely, adopt a memory-safe language.
QwenGlazer9000 · · focus · HN ↗
edgyquant · · focus · HN ↗
bryanlarsen · · focus · HN ↗
<a href="https://ladybird.org/posts/adopting-rust/" rel="nofollow">https://ladybird.org/posts/adopting-rust/
Myself, my annoyance with Ladybird is that restarted everything from scratch. There are components of servo that are really good and basically complete. Why not use those components and concentrate on the components where you have design conflicts with Servo?
cogman10 · · focus · HN ↗
To me it's just not serious. They also had articles of "why we are doing zig and not rust".
It's an ambitious project, but I can't take it seriously when the tech stack is in constant flux.
askonomm · · focus · HN ↗