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?
Their origins are in C++, which is what SerenityOS has used. They've never done zig. They explored using Swift as a C++ successor language for the project[1], but seeing the platform support out of Apple was lacking, they gave up and made the bet on Rust[2].
The motivation to use a memory safe language as the alpha approaches sounds more of a longer term bet [3].
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.
julenx · · focus · HN ↗
The motivation to use a memory safe language as the alpha approaches sounds more of a longer term bet [3].
[1] <a href="https://ladybird.org/newsletter/2024-11-30/#swift-language-adoption" rel="nofollow">https://ladybird.org/newsletter/2024-11-30/#swift-language-a...
[2] <a href="https://ladybird.org/posts/adopting-rust/" rel="nofollow">https://ladybird.org/posts/adopting-rust/
[3] <a href="https://ladybird.org/posts/changing-how-we-develop-ladybird/" rel="nofollow">https://ladybird.org/posts/changing-how-we-develop-ladybird/