this post was submitted on 23 Feb 2026
123 points (80.3% liked)

Technology

81797 readers
4488 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related news or articles.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots


founded 2 years ago
MODERATORS
 

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
[–] greyfrog@sh.itjust.works 2 points 18 hours ago (1 children)

Surely you read the article?

"The requirement from the start was byte-for-byte identical output from both pipelines. "

The bytecode from C++ is identical to the Rust output.

[–] WhyJiffie@sh.itjust.works 2 points 15 hours ago* (last edited 15 hours ago)

~~I don't think it's possible to write rust code that compiles to the exact same binary as c++. compilers make different optimizations, and make overall a different structure, especially across languages.~~

~~I think they meant the rust library produces the same output from the same input as the c++ library.~~

if llms indeed generate worse rust code than for other languages, that's not that big of a problem because the compiler will catch a lot of mistakes. if it compiles, it will run, and no memory safety bugs unless unsafe is also used. the llm could pick the wrong functions for some uses, but that should be caught relatively easily with testing, which can be automated partly

edit: I was wrong, they indeed say that. this is weird.