Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Wedeo – a Rust Rewrite of FFmpeg

github.com

Post reply on HN
Print view View original

31–32 of 32 posts

Re: Wedeo – a Rust Rewrite of FFmpeg

#31

Post by jdiff »

sharifhsn wrote: post #27
jdiff wrote: post #25

Earlier quoted context omitted.

Because it can't. I'm aware of only two projects that have attempted this. 1. Anthropic's C compiler. This is a buggy, unoptimized, unwieldy mess. One that can compile the Linux kernel, which is no mean feat. But it is not "fully featured." And it had an incredible array of tests to start with. 2. Cursor's web browser. This is, flatly, a trainwreck. It's built on top of massive dependencies that do incredible amounts…

The tests are the real clincher here. That’s the main reason that this project has made so much progress: the FATE suite highlights specific bugs to fix and tracks regressions. As for optimization, that seems to be more of a question of effort than whether it’s possible. I was able to take down the performance gap on Rust vs C (without Assembly) from 10x to 1.5x through detailed profiling and iterative improvements w…

Anthropic's C compiler also had an incredible test suite available, and was trained on compiler codebases. It might have been built "from scratch" but compilers are incredibly well-trodden ground.

And to contrast, Cursor's browser explicitly reviewed Servo's architecture before setting out, and still wound up like that.

Re: Wedeo – a Rust Rewrite of FFmpeg

#32

Post by sharifhsn »

jdiff wrote: post #31
sharifhsn wrote: post #27

Earlier quoted context omitted.

The tests are the real clincher here. That’s the main reason that this project has made so much progress: the FATE suite highlights specific bugs to fix and tracks regressions. As for optimization, that seems to be more of a question of effort than whether it’s possible. I was able to take down the performance gap on Rust vs C (without Assembly) from 10x to 1.5x through detailed profiling and iterative improvements w…

Anthropic's C compiler also had an incredible test suite available, and was trained on compiler codebases. It might have been built "from scratch" but compilers are incredibly well-trodden ground. And to contrast, Cursor's browser explicitly reviewed Servo's architecture before setting out, and still wound up like that.

The difference between using general knowledge and summaries and doing code-for-code rewrites cannot be understated. When creating `wedeo`, despite DIRECTLY reviewing FFmpeg's code, Claude would frequently make mistakes that would have to be fixed. I would constantly have it go and refer back to the ground truth FFmpeg source implementation. It did eventually work, but only after several rounds of reviews, and often dead-end investigations. Being able to directly inspect (and in some cases modify for extra debug output) FFmpeg at any given time was invaluable, and I doubt any rewrite would succeed without having that.
Post reply on HN