News for hackers. Stuff that matters.
Re:Today, we hacked what we'd set out to hack: the iPhone by anthk on Friday October 23, 2026 @02:42PM (#50213560)
If I were Google I'd try to rewrite Chromium in Rust. The FFMPEG folks should try porting the whole codebase to Rust too. They can always keep the legacy versions for legacy computers (my old n270 netbook can barely play 720p@30FPS anyway, and it's too slow to downsize 4k video to 720 or 480p...), so a bigger amd64 machine will always be -reallistically- needed for anything else than <=720p consumption.
Re:Today, we hacked what we'd set out to hack: the iPhone by nkjoep on Friday October 23, 2026 @03:54PM (#50214452)
What folks at Ladybird did this year. Started adopting rust for part if not all their engine.
Re:Today, we hacked what we'd set out to hack: the iPhone by notpushkin on Monday October 26, 2026 @02:43AM (#50239954)
After trying out Swift first!
Re:Today, we hacked what we'd set out to hack: the iPhone by QuantumNomad_ on Saturday October 24, 2026 @06:37AM (#50219941)
> The FFMPEG folks should try porting the whole codebase to Rust too.

They don’t seem convinced that that would be a meaningful use of time for them. (2025)

https://itsfoss.com/news/ffmpeg-swipe-at-rust/

And 6 months ago someone did a little experiment using Claude to rewrite FFmpeg in Rust. It was by the own description by the person that had the AI do it, significantly slower than FFmpeg even when incorporating assembly code from FFmpeg.

https://github.com/sharifhsn/wedeo

Maybe with further advancements it is now possible to get a better result, or soon.

But if you are going to copy their assembly code into the Rust protect how do you definitively prove that no memory unsafe operations are happening in those parts? Seems to me that either the whole thing should be safe Rust, if the point of the rewrite is memory safety.