From: Nicolas George <george@nsup.org> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [RFC] fftools/ffmpeg and libavdevice/sdl issue Date: Thu, 14 Dec 2023 10:35:56 +0100 Message-ID: <ZXrMfMZibVTI1nqe@phare.normalesup.org> (raw) In-Reply-To: <170254011817.8914.11563902500718557350@lain.khirnov.net> Anton Khirnov (12023-12-14): > As mentioned elsewhere in the thread, you can just as well pipe raw > video in yuv4mpeg or nut to the video player of your choice and thus As was already mentioned elsewhere in the thread, this solution has a lot more drawbacks. > avoid all these hacks. Please refrain from calling other people's work hacks. > I have to strongly disagree. This is neither practically workable, > nor a good goal to aim at. And I strongly agree with Stefano. Having the tools just thin wrappers around the libraries is the only way to ensure the libraries are maximally useful for other applications. Otherwise, useful code will only reside in the tools and be only available through a clumsy command-line interface. > This mindset IMO inevitably leads to (among > other problems): > * endless scope creep > * bloated, inefficient, and buggy libraries, trying (and failing) to > support every use case under the sun > * myopic API design aimed at fulfilling the needs of precisely one > caller; this is a problem e.g avfilter badly suffers from, and to a > lesser extent avformat I see no argument supporting this opinion of yours. Quite the opposite, over the years, Stefano and others, including me, have made some headway in this direction without hitting these pitfalls. -- Nicolas George _______________________________________________ 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".
next prev parent reply other threads:[~2023-12-14 9:36 UTC|newest] Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-12 17:27 Zhao Zhili 2023-12-12 18:04 ` Nicolas George 2023-12-13 4:19 ` Zhao Zhili 2023-12-13 17:30 ` [FFmpeg-devel] Mailinglist conduct [was: [RFC] fftools/ffmpeg and libavdevice/sdl issue] Ronald S. Bultje 2023-12-13 9:08 ` [FFmpeg-devel] [RFC] fftools/ffmpeg and libavdevice/sdl issue Anton Khirnov 2023-12-13 9:31 ` Zhao Zhili 2023-12-13 10:06 ` Anton Khirnov 2023-12-13 10:37 ` Zhao Zhili 2023-12-13 10:45 ` Nicolas George 2023-12-13 10:49 ` Anton Khirnov 2023-12-13 9:44 ` Nicolas George 2023-12-14 0:47 ` Stefano Sabatini 2023-12-14 7:48 ` Anton Khirnov 2023-12-14 9:35 ` Nicolas George [this message] 2023-12-16 15:18 ` Stefano Sabatini 2023-12-18 17:33 ` Anton Khirnov 2023-12-18 19:58 ` Michael Niedermayer 2023-12-18 20:02 ` Nicolas George 2023-12-19 7:23 ` Rémi Denis-Courmont 2023-12-19 9:29 ` Nicolas George 2023-12-19 10:43 ` Rémi Denis-Courmont 2023-12-19 12:51 ` Nicolas George 2023-12-19 14:47 ` Rémi Denis-Courmont 2023-12-19 16:58 ` Michael Niedermayer 2023-12-19 18:48 ` Rémi Denis-Courmont 2023-12-19 18:55 ` Nicolas George 2023-12-19 19:36 ` Michael Niedermayer 2023-12-15 12:37 ` Alexander Strasser via ffmpeg-devel
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=ZXrMfMZibVTI1nqe@phare.normalesup.org \ --to=george@nsup.org \ --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