From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ffbox0-bg.mplayerhq.hu (ffbox0-bg.ffmpeg.org [79.124.17.100]) by master.gitmailbox.com (Postfix) with ESMTP id 9F68C46A6E for ; Wed, 2 Aug 2023 12:55:31 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 13F2168C624; Wed, 2 Aug 2023 15:55:30 +0300 (EEST) Received: from relay4-d.mail.gandi.net (relay4-d.mail.gandi.net [217.70.183.196]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id DFC5468C618 for ; Wed, 2 Aug 2023 15:55:22 +0300 (EEST) Received: by mail.gandi.net (Postfix) with ESMTPSA id 4E3CAE000C for ; Wed, 2 Aug 2023 12:55:22 +0000 (UTC) Date: Wed, 2 Aug 2023 14:55:21 +0200 From: Michael Niedermayer To: FFmpeg development discussions and patches Message-ID: <20230802125521.GG7802@pb2> References: MIME-Version: 1.0 In-Reply-To: X-GND-Sasl: michael@niedermayer.cc Subject: Re: [FFmpeg-devel] What is FFmpeg and what should it be X-BeenThere: ffmpeg-devel@ffmpeg.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: FFmpeg development discussions and patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: FFmpeg development discussions and patches Content-Type: multipart/mixed; boundary="===============2828372471906224180==" Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: --===============2828372471906224180== Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="yzCAVeWw9RvyYzgB" Content-Disposition: inline --yzCAVeWw9RvyYzgB Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi Vittorio On Wed, Aug 02, 2023 at 03:44:13AM +0200, Vittorio Giovara wrote: > On Sun, Jul 30, 2023 at 3:04=E2=80=AFPM Nicolas George = wrote: >=20 > > Kieran Kunhya (12023-07-28): > > > FFmpeg doesn't implement TCP in userspace, it doesn't implement the > > > WiFi protocol etc etc. Different layers are delegated to different > > > programs. > > > > Hi. You seem to be discussing this in more good faith than I previously > > imagined, so I will try to tone done the irritation in my mails. > > >=20 > sorry for jumping in mid discussion, but shouldn't that be the case alway= s? >=20 > But if people started to routinely use FFmpeg on some kind of > > bare-metal microcontroller where network hardware exists but the > > official network stack is too big to share the space with FFmpeg, and if > > somebody were to propose a limited network stack based on lavu's > > cryptographic primitives, then it would totally make sense to accept it. > > >=20 > no? that sounds a terrible maintenance burden in terms of both code size > and security issues, nobody wants that! > what could be a viable compromise is *maybe* providing the hooks where > needed where custom io and callbacks can be implemented, but afaict there > are plenty of those in ffmpeg already >=20 > FFmpeg has been successful because it relied on pragmatism rather than > > dogmatic adherence to principles. Let us continue that way. > > >=20 > ffmpeg has been successful because points of contentions were resolved wi= th > consensus (most of the times) and not by sheer number of emails or email > length about the topic. I am not even familiar with this avradio thing but > if the community seems so against it, let's maybe find another solution > (separate library, repository, tool etc) instead of wasting time and ener= gy > over the same points. the code already is in a seperate repository. And is basically isolated in a single demuxer and single input device. Some people still complain that it exists About the community i do not know what the majority wants. About users iam fairly confident that they prefer having the option to use it than not having the option. thx [...] --=20 Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB it is not once nor twice but times without number that the same ideas make their appearance in the world. -- Aristotle --yzCAVeWw9RvyYzgB Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iF0EABEIAB0WIQSf8hKLFH72cwut8TNhHseHBAsPqwUCZMpSOQAKCRBhHseHBAsP q1kIAKCSY8lkMhId+sCIt2hiwaeJ1J+zfgCeMiK6VUhTKirA6aOyMVUzhyuHU3g= =2RF+ -----END PGP SIGNATURE----- --yzCAVeWw9RvyYzgB-- --===============2828372471906224180== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ 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". --===============2828372471906224180==--