FFmpeg is one of the most widely used open source multimedia frameworks globally, with it powering audio and video processing for applications like VLC, OBS Studio, HandBrake, Jellyfin, etc. and being widely used in live-streaming, including platforms like Twitch.
On the other hand, rav1d is a new Rust-based decoder developed by Prossimo that aims to be a memory-safe reimplementation of the C-based dav1d decoder, which is widely recognized as the fastest software AV1 decoder in use across multiple platforms.
A recent post by FFmpeg has reignited conversation surrounding the trade-offs between performance, cost, and memory safety when building such critical systems.
FFmpeg is Not Impressed
Rust is so good you can get paid $20k to make it as fast as C:https://t.co/HVDokmLk5r
— FFmpeg (@FFmpeg) May 15, 2025
Commenting on Prossimo's recent performance bounty program for rav1d, FFmpeg mentioned that "Rust is so good you can get paid $20k to make it as fast as C". That looks like a direct jab at Rust and the rav1d decoder to me. 😲
The performance bounty has set out to close a performance gap where rav1d is ~5% slower than dav1d. Prossimo is offering a sizable $20,000 as a reward for anyone who manages to close the gap.
They have put out a bunch of rules that restrict pretty much most of the world from contributing, limiting this bounty only to certain regions and excluding a large portion of the global developer community.
Are they Right?
The information technology industry has been steadily moving towards Rust, a programming language known for its memory safety and performance. The U.S. White House even formally endorsed the shift towards memory-safe programming languages in a 2024 report from the Office of the National Cyber Director (ONCD).
However, the push for Rust adoption hasn't been without controversy. One such instance is the effort to integrate it into the Linux kernel, which has faced resistance and internal tension, with a recent occurrence causing friction and resulting in the creation of a Rust kernel policy to prevent future conflicts.
Despite growing adoption, many in the developer community continue to question whether Rust’s benefits truly outweigh those of longstanding languages like C.
From It's FOSS News via this RSS feed
These are all the old arguments Assembly threw at C when C started taking over. Now it's C's turn to be put out to pasture and it's rolling out the same complaints.
C had decades to solve its security problems and has not been successful enough. It's time for a new standard.
If you need faster than Rust and can afford the security issues, run C. If you need faster than C and have some top talent, use Assembly. If you need it faster and can afford the ASIC, use Verilog/VHDL. If you need faster and can afford a fab plant, start laying out your transistors with tape and a light table.