126
Ladybird Browser adopts Rust, with help from AI (ladybird.org)
submitted 8 months ago by to c/technology@lemmy.world
85 comments fedilink hide all child comments
 

Lobsters.

We’ve been searching for a memory-safe programming language to replace C++ in Ladybird for a while now. We previously explored Swift, but the C++ interop never quite got there, and platform support outside the Apple ecosystem was limited. Rust is a different story. The ecosystem is far more mature for systems programming, and many of our contributors already know the language. Going forward, we are rewriting parts of Ladybird in Rust.

you are viewing a single comment's thread
view the rest of the comments
[–] 10 points 8 months ago (3 children)

The things people criticize are so fucking brainless these days. AI this, slop that.

Not a single one of you made fun of "let's rewrite it in Rust." You can't even elevate to the level of mildly funny parroting.

  • permalink
  • fedilink
  • source
  • hideshow 3 child comments
    •
  • [–] 7 points 8 months ago (2 children)

    “Let’s stop halfway through our multi-year project to rewrite it in another language” is peak nerd shiny distraction. I say this as one who resists the urge every day. Way to delay your project by several more years, clown.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 3 points 8 months ago (1 child)

    All things considered the way they're approaching the migration is fine enough - they're only moving specific portions at a time, they're not stopping C++ development, and they're making sure it doesn't introduce regressions. Adopting a memory-safe language for something like a browser makes sense because it completely eliminates that class of vulnerabilities.

    The problem is the way they're approaching the code itself. From their wording, it sounds like they're relying on AI heavily for both writing and reviewing the code. Rust has a steeper learning curve than most languages and is very different from C++. They even mention in the blog that their current Rust code looks like C++ code ported over. If they don't take the time to actually learn Rust before adopting it, it'll just lead to security logic issues that their AI couldn't catch because C++ and Rust don't always behave the same way. And that's completely ignoring all of the other ethical/technical issues with AI

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 4 points 8 months ago

    Be that as it may, the time to choose Rust was at the beginning. It existed then, but they made their technology choice. Continuing to develop in C++ while doing the migration just means more throwaway code and duplicated effort. This decision is truly the worst of both worlds.

  • permalink
  • fedilink
  • source
  • parent