Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: "Rémi Denis-Courmont" <remi@remlab.net>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH 2/2] avcodec: remove sonic lossy/lossless audio
Date: Wed, 28 Feb 2024 22:23:24 +0200
Message-ID: <155378831.aaO8PmNeeh@basile.remlab.net> (raw)
In-Reply-To: <cb3a3cb2-a8a4-46a1-838f-80df2e3aec2c@gmail.com>

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-request@ffmpeg.org with subject "unsubscribe".

  parent reply	other threads:[~2024-02-28 20:23 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-28 12:56 [FFmpeg-devel] [PATCH 1/2] MAINTAINERS: remove inactive developer J. Dekker
2024-02-28 12:56 ` [FFmpeg-devel] [PATCH 2/2] avcodec: remove sonic lossy/lossless audio J. Dekker
2024-02-28 13:23   ` Andreas Rheinhardt
2024-02-28 13:29   ` Michael Niedermayer
2024-02-28 13:31     ` J. Dekker
2024-02-28 13:41       ` Nicolas George
2024-02-28 13:57       ` Vittorio Giovara
2024-02-28 14:08         ` J. Dekker
2024-02-28 17:55       ` James Almer
2024-02-28 18:36         ` Jean-Baptiste Kempf
2024-03-10 13:12           ` Alexander Strasser via ffmpeg-devel
2024-02-28 20:23         ` Rémi Denis-Courmont [this message]
2024-02-28 22:13     ` Lynne
2024-02-29  1:50       ` Vittorio Giovara
2024-02-29 13:30         ` Lynne
2024-02-29 14:44           ` Vittorio Giovara
2024-03-01  1:13             ` Michael Niedermayer
2024-03-10 19:45               ` Leo Izen
2024-03-01 18:59           ` Anton Khirnov
2024-03-01 19:03             ` Nicolas George
2024-03-01 19:41             ` Lynne
2024-03-01 20:33               ` Anton Khirnov
2024-03-01 21:34                 ` Lynne
2024-03-02 13:33                   ` Vittorio Giovara
2024-03-01 20:14   ` Tomas Härdin
2024-02-28 14:38 ` [FFmpeg-devel] [PATCH 1/2] MAINTAINERS: remove inactive developer Vittorio Giovara

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=155378831.aaO8PmNeeh@basile.remlab.net \
    --to=remi@remlab.net \
    --cc=ffmpeg-devel@ffmpeg.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
		ffmpegdev@gitmailbox.com
	public-inbox-index ffmpegdev

Example config snippet for mirrors.


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git