From: "Rémi Denis-Courmont via ffmpeg-devel" <ffmpeg-devel@ffmpeg.org>
To: ffmpeg-devel@ffmpeg.org
Cc: "Rémi Denis-Courmont" <remi@remlab.net>
Subject: [FFmpeg-devel] Re: [RFC] C++
Date: Wed, 22 Oct 2025 21:50:27 +0300
Message-ID: <12491913.6GWE5blU8g@basile.remlab.net> (raw)
In-Reply-To: <3508f2b1-30f5-4c21-8317-9bc856d42373@rothenpieler.org>
Le keskiviikkona 22. lokakuuta 2025, 21.12.47 Itä-Euroopan kesäaika Timo 
Rothenpieler via ffmpeg-devel a écrit :
> They allow a distributor to do it centrally, and don't burden it onto 
> every single developer.
And? Neither does Cargo? It does not force developers to pin anything. It's 
*recommended* to pin if (and only if) shipping a final application or OS, 
rather than libraries, i.e. unless you're the distributor.
Obviously someone is going to have to be burdened with checking versions and 
bugs at some point in the supply chain, with the user as the last resort - 
that's true for any programming language.
> > Cargo gives you the *choice* of pinning or not pinning the versions
> > through the lock. FFmpeg should *probably* not pin anything and just
> > specify minimum version requirements. And it'll be the exact same
> > dependency hell that we already have (or don't have - that's subjective)
> > with C. Nothing to see here.
> 
> Given that API stability is far from a given in that world,
It's no more or less stable than C. It is far better than C++ where you need 
to be super careful and bend over backward not to leak object type layouts 
through public headers.
> not pinning  anything does not sound like a good idea.
And yet FFmpeg is not currently pinning any existing dependencies. This has 
nothing to do with using C++ or Rust really.
> I'd rather just not enter that dependency hell at all.
Sure, you do that by not having dependencies. That's an argument against 
external dependencies (which I can get behind), and it is also an argument 
against C++ which requires a runtime even if you don't touch the STL.
By design, you can do C, Rust or a mix of both, without dependencies  - as 
exemplified by the Linux kernel. It's just a matter of project policy. FWIW, 
Rust is actually handling this more consistently and flexibily than C, since it 
provides an intermediate point between freestanding and hosted environment - 
not that FFmpeg supports anything less than a hosted environment.
-- 
ヅニ-クーモン・レミ
Hagalund ny stad, f.d. Finska republik Nylands
_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org
next prev parent reply	other threads:[~2025-10-22 18:50 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-20 17:50 [FFmpeg-devel] " Tomas Härdin via ffmpeg-devel
2025-10-20 21:34 ` [FFmpeg-devel] " Neal Gompa via ffmpeg-devel
2025-10-21  2:24 ` Lynne via ffmpeg-devel
2025-10-22  8:57   ` Tomas Härdin via ffmpeg-devel
2025-10-22 10:46   ` Tomas Härdin via ffmpeg-devel
2025-10-21 18:41 ` Niklas Haas via ffmpeg-devel
2025-10-22  3:15 ` Romain Beauxis via ffmpeg-devel
2025-10-22  4:19   ` InnocentZero via ffmpeg-devel
2025-10-22  8:24   ` Nicolas George via ffmpeg-devel
2025-10-22 10:53   ` Tomas Härdin via ffmpeg-devel
2025-10-22 12:09 ` Gregor Riepl via ffmpeg-devel
2025-10-22 12:42   ` Michael Niedermayer via ffmpeg-devel
2025-10-22 13:07   ` Timo Rothenpieler via ffmpeg-devel
2025-10-22 17:07     ` Rémi Denis-Courmont via ffmpeg-devel
2025-10-22 18:12       ` Timo Rothenpieler via ffmpeg-devel
2025-10-22 18:50         ` Rémi Denis-Courmont via ffmpeg-devel [this message]
2025-10-22 17:08   ` Rémi Denis-Courmont via ffmpeg-devel
2025-10-23 21:45   ` Tomas Härdin via ffmpeg-devel
2025-10-22 13:05 ` Michael Niedermayer via ffmpeg-devel
2025-10-23 21:49   ` Tomas Härdin via ffmpeg-devel
2025-10-23 22:24     ` Michael Niedermayer via ffmpeg-devel
2025-10-22 14:03 ` Leo Izen via ffmpeg-devel
2025-10-21 14:47 Zhao Zhili via ffmpeg-devel
2025-10-21 14:58 ` Nicolas George via ffmpeg-devel
2025-10-21 15:31   ` Zhao Zhili via ffmpeg-devel
2025-10-22  1:34     ` Michael Niedermayer via ffmpeg-devel
2025-10-22  8:11     ` Nicolas George via ffmpeg-devel
2025-10-22  9:15       ` Zhao Zhili 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=12491913.6GWE5blU8g@basile.remlab.net \
    --to=ffmpeg-devel@ffmpeg.org \
    --cc=remi@remlab.net \
    /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