Earlier quoted context omitted.
The language is actually something that makes me look elsewhere. We already have enough sufficiently vulnerable browsers and other network related software. Choosing C/C++ as language may work to make something that works, and it may be in the realm of experience the people building it have. However, it does not make this browser stand out in terms of security/safety. While they may deliver tremendous work, that work…
As stated elsewhere, the Ladybird team expects to move to Swift. There are still a couple blockers keeping them from doing so. They have actively rejected Rust as they see it as unsuitable for a heavily OOP code base. They see OOP as a great fit for implementing the web spec.
I am far from a Rust expert. Only have tried it some time ago. I think Rust does a good job with forcing composition over inheritance, steering towards the approaches, that have been found to be superior to deep inheritance hierarchies, by its concepts of structs and traits implemented for structs, and not having classes. Of course, if one equates OOP with classes and inheritance, then Rust will not meet that definition of OOP.