Le keskiviikkona 28. helmikuuta 2024, 19.55.11 EET James Almer a écrit : > > The last commit which actually changed the codec was > > 6026a5ad4f135476c7a1f51f8cfa7f4cc2ca0283 by you in 2013 which is over 10 > > years ago. For an experimental codec I think it's pretty safe to say > > that development has stalled. > > > > Keeping the codec around based on 'what if?'s doesn't seem > > reasonable. Besides, if you do make sonic the most advanced audio codec > > in FFmpeg there's nothing which says you couldn't re-add it at a later > > date when it's being actively developed again. > > Does it hurt keeping it around?
Considering the sheer number of audio codecs in libavcodec, the difference is peanuts. But in principle, any dead code is an extra maintenance burden, whether it be reported security vulnerabilities that "need" to be fixed to appease Linux distros and corporate freeloaders, or to update the internal interfaces. > If it can at some point be developed > again, then removing the codec id to re-add it later will be a bit dirty. Slightly, but the chance of that seem almost zero. Also compared to moving stuff in and out of staging like the kernel does, or between good, bad and ugly like a certain competing OSS framework does, it's pretty much nothing. People are not going to ditch FFmpeg on the basis of misusing the VCS over that hypothetical. -- 雷米‧德尼-库尔蒙 http://www.remlab.net/ _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
