HackerX

Account

@FFmpeg

Ideas
2
Recommendations
5
HN citations
8
Open Source1Programming1
View @FFmpeg on X

@FFmpeg

Open Source

@FFmpeg

View on X
Recommended by 3 HN users
From the Hacker News threadMy apologies - you’re correct. I didn’t mean that as “you should never expect anyone to have contributed code for free/the pleasure/for the puzzle solving aspect”. I do it all of the time. I meant - it’s unfair to consider that because this labor “fell from the sky”, you should just accept it - and as others have said, in the case of projects that become popular, that the burden should just automatically fall on the shoulders of someone who happened to share code “for free”. If/when someone ends up becoming responsible for work they hadn’t necessarily signed up for (who signs up for burnout?) - it’s ok/necessary/mandatory to see how everyone (and or Nvidia/Google/OpenAI etc) can, like, help. My insistence is on the opt-out nature of this so that people who would be ok being compensated don't have to beg. Consider how the xz malware situation happened [0]. Or the header & question 8 from the FAQ for PocketBase [1]. [0] x.com/FFmpeg/status/1775178803129602500 [1] pocketbase.io/faq/@gregsadetskyGitHub should charge everyone $1 more per month to fund open source2026
3

@FFmpeg

Programming

@FFmpeg

View on X
Recommended by 2 HN users
From the Hacker News threadFFmpeg developers aren't stupid and aren't doing things because of historical accident. If you don't mind writing platform specific code, it simply works better this way. Here's clang messing up x86 intrinsics code. x.com/ffmpeg/status/1852913590258618852 The other reason to do it is that, since x86 intrinsics are named in Hungarian notation, they're so hard to read that the asm is actually more maintainable.@astrangeA 94x speed improvement demonstrated using handwritten assembly2024
2

More

RSS feed

Keyboard shortcuts