Ladybird Rewrite Flirts with Rust Abyss: Experts Warn LLMs Might Trap Code Between Pure Rust or Deep C++ Pits
The push to rewrite parts of the Ladybird browser in Rust gained concrete momentum, with one contributor, 'darkkite,' documenting the successful, high-fidelity porting of 25,000 lines of code to Rust over two weeks, claiming byte-for-byte accuracy.
The debate over method rages. Proponents like 'SwooshBakery624' argue Rust offers a superior, mature systems ecosystem compared to Swift. Conversely, critics like 'racketlauncher831' flag the entire strategy as risky, particularly the reliance on LLMs for code generation, suggesting C++ retention is safer. Furthermore, the technical difficulty of marrying Rust with a deep C++ OOP hierarchy is cited by 'FizzyOrange,' suggesting clean modular splits are inevitable.
The community splits sharply between valuing Rust's safety guarantees and fearing the implementation chaos. The core fault line remains the adoption methodology: trust the AI-assisted port, or reject the risk inherent in forcing Rust into established C++ structures.
Key Points
Rust's technical superiority for systems programming compared to previous options.
'SwooshBakery624' argues Rust provides a more mature ecosystem and better cross-platform support than Swift.
The danger of using LLMs for core codebase generation.
'racketlauncher831' questions the adoption strategy, viewing LLM reliance as introducing unnecessary risk, suggesting sticking with C++.
The inherent difficulty of integrating Rust code into deep C++ OOP structures.
'FizzyOrange' asserts that mixing code will likely force rewrites into entirely monolithic Rust or C++ modules.
The manageable scope and success of AI-assisted, high-fidelity porting.
'darkkite' minimized risk by achieving a documented 25,000-line, byte-for-byte Rust port in weeks.
The project's ongoing development creates instability during the rewrite.
'chonglibloodsport' points out the high risk from rewriting while actively developing new features, keeping the target constantly moving.
Source Discussions (3)
This report was synthesized from the following Lemmy discussions, ranked by community score.