On Mon, 11 Dec 2017 14:22:43 +0100
Paul B Mahol <one...@gmail.com> wrote:

> On 12/11/17, Hendrik Leppkes <h.lepp...@gmail.com> wrote:
> > On Mon, Dec 11, 2017 at 12:07 PM, Paul B Mahol <one...@gmail.com> wrote:  
> >>>
> >>> Fine, but it's inevitable that the encoder supports the J formats still
> >>> for a while.  
> >>
> >>
> >> Why are you all dismissive about this?  
> >
> >
> > Because we have an established way to remove things like this, and
> > that doesn't happen over night.
> > Its not ok for stuff to stop working without a replacement in place
> > for a sufficient time before that, so people can migrate.
> >
> > First, implement replacement and add visible deprecation messages -
> > and then wait the established deprecation period before actually
> > removing it.  
> Bullshit, J formats are deprecated for ages.

Yeah, this has been a favorite thing of mine, how the J formats have
been deprecated for almost a decade, yet API users can't avoid using
them, and even ffmpeg CLI will complain about them in a completely
nonsense way.

You need another layer of deprecation now, because tons of software
will probably use those formats, even though they're deprecated, and
users have no way of knowing that they're _actually_ considered
deprecated now and might _actually_ go away and there's _actually_ a
way to avoid them now.

The situation is pretty awesomely fucked.
ffmpeg-devel mailing list

Reply via email to