4 ms·
The amount of armchair quarterbacking here is wild.
by akerl_ 10mo ago
The amount of armchair quarterbacking here is wild.
- rvnx 10mo agoThen waiting to see how they addressed these points and what were the approaches taken and why ? Here spent time to think and document all the IRC chats, the Twitter thread, the attitude of the SoC manufacturer, etc. There has to be a backstory to suddenly come after 1.5 years for an issue that could have been solved in 10 minutes.
- kelnos 10mo agoThen why didn't Rockchip solve it in 10 minutes?
- rvnx 10mo agoBad decision and risk/reward calculation for sure. If it's code that is core to your stuff, and it is GPL'd, it's (technically) very tricky to solve. But here, as FFmpeg is LGPL and we talk about one single file, there is even less work to do in order to fix that.
- justinclift 10mo agoYeah, Rockchip seems to have screwed up badly but as per the GitHub DCMA notice: https://github.com/github/dmca/blob/master/2025/12/2025-12-18-ffmpeg.md https://github.com/github/dmca/blob/master/2025/12/2025-12-1... > ... the offending repository maintainers were informed of the problem almost 2 years ago ([private]), and did nothing to resolve it. Worse, their last comment ([private]) suggests they do not intend to resolve it at all. Seems like the reporter gave them a lot of time to fix the problem, then when it because obvious (to them) that it was never going to be fixed they took an appropriate next step.