This is the reason why mediabunny is such a good project. A developer who cares about good software craft and isn’t tied to just a language or paradigm.
It's written in Zig, which allows me to use WASM which enables a bunch of CPU instructions not reachable via JavaScript. And then it's a bunch of things: I avoid branches in the hot paths, I use SIMD wherever possible, and I use ILP (instruction-level parallelism) to have a single CPU core process multiple data streams at once.
A lot of is just: I write the naive version first, then see where I'm doing too much work, change the code, measure, and repeat this 500 times
This guy built a local "video -> HLS -> R2" to pipeline, which is cool, but he uses an FFmpeg script to do it. The same task could've been achieved with Mediabunny in about ~10 lines of code, would not need a script, and would probably run 5x faster due to proper HW acceleration.
The thing is: it's not like he didn't use Mediabunny because he hated it. He probably just didn't know Mediabunny existed or that it could do this. Marketing really is hard!
Mediabunny 1.42.0 is now out, adding THE most requested feature: full read/write support for HLS! 🚀
It's truly a game changer for client-side media processing. Here, I'm creating 5 renditions from a 40-second video in ~10 seconds, fully client-side, without a transcode server:
@mitsuhiko I think it's just part of how slang evolves, hard to pin point to something specifically. But I also share your observation, it seems a lot more prominent in the Twitter tech bubble.
@SebAaltonen With 365*65 (assuming very young people dont have wallets) possibilities and checks whether the phone numer is valid I wonder how long brute forcing the number would take.