← Back to context

Comment by jvillasante

1 day ago

> We’ve been searching for a memory-safe programming language to replace C++ in Ladybird for a while now.

The article fails to explain why. What problems (besides the obvious) have been found in which "memory-safe languages" can help. Do these problems actually explain the need of adding complexity to a project like this by adding another language?

I guess AI will be involved which, at this early point in the project would make ladybird a lot less interested (at least to me).

> What problems (besides the obvious) have been found in which "memory-safe languages" can help.

Why isn't that enough?

Browsers are incredibly security-sensitive projects. Downloading untrusted code from the internet and executing is part of their intended functionality! If memory safety is needed anywhere it's in browsers.

Even Chrome has started to adopt Rust due to recurring memory vulnerabilities.... that's a big enough reason.

You don't want a browser with a bunch of RCEs that can be triggered by opening a web page...

  • You do want a browser with RCE, but you want it to keep the it sandboxed. The hard part is executing the code safely