Web Engines Hackfest 2023 - https://webengineshackfest.org/2023Title: Ladybird: Building a new browser from scratchAuthor: Andreas KlingDate: 05/06/2022Slide...
He does, but the title makes it sound like he’s criticising when he’s just explaining some context.
He says they write their engines to be closely modelled on the specs, and that the web and the web spec is an object-oriented platform.
When asked if he’d use another language for Ladybird he first answers Swift - well actually he first jokes that he’d first design a new language, then says that he looked at Rust and likes a lot of things about it. When asked about why-not-Rust he says he likes OO languages and this project should be in an OO language because so is the spec, and Rust is not OO-friendly, “it’s, like, OO-hostile”.
That’s probably why I like Rust so much. I’ve felt for a long time now that after the concept of null, the widespread embrace of OO is probably the second worst decision in programming. While it was certainly better than the goto hell that preceded it, inheritance I think has ultimately proven to be a trap.
To be fair, OO is not so strictly linked to inheritance, and one could conceive Rust structs and traits as a sort of OO system in some ways. For example, in the way that different struct types may implement a given trait and run a method with a common name and interface.
Still, I would say the design Rust accommodates is different from typical OO design.
He does, but the title makes it sound like he’s criticising when he’s just explaining some context.
He says they write their engines to be closely modelled on the specs, and that the web and the web spec is an object-oriented platform.
When asked if he’d use another language for Ladybird he first answers Swift - well actually he first jokes that he’d first design a new language, then says that he looked at Rust and likes a lot of things about it. When asked about why-not-Rust he says he likes OO languages and this project should be in an OO language because so is the spec, and Rust is not OO-friendly, “it’s, like, OO-hostile”.
That’s probably why I like Rust so much. I’ve felt for a long time now that after the concept of null, the widespread embrace of OO is probably the second worst decision in programming. While it was certainly better than the goto hell that preceded it, inheritance I think has ultimately proven to be a trap.
To be fair, OO is not so strictly linked to inheritance, and one could conceive Rust structs and traits as a sort of OO system in some ways. For example, in the way that different struct types may implement a given trait and run a method with a common name and interface.
Still, I would say the design Rust accommodates is different from typical OO design.