From: Michael Niedermayer <michael@niedermayer.cc> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] I've written a filter in Rust Date: Sun, 23 Feb 2025 22:51:44 +0100 Message-ID: <20250223215144.GS4991@pb2> (raw) In-Reply-To: <313bfd57b0e976df1845c160eeb60898baf6d0fb.camel@haerdin.se> [-- Attachment #1.1: Type: text/plain, Size: 1613 bytes --] Hi On Sun, Feb 23, 2025 at 10:30:03PM +0100, Tomas Härdin wrote: > lör 2025-02-22 klockan 14:57 +0200 skrev Rémi Denis-Courmont: > > Le perjantaina 21. helmikuuta 2025, 20.02.16 UTC+2 Tomas Härdin a écrit : > > > The above said, I'm not against Rust. It has some nice properties. But > > > it does not seem very "stable" so far. Perhaps this has changed in > > > recent years.. > > > > IME, it's become very usable for user-space code. Bare metal still pretty much > > requires unstable features, but that's not a problem for FFmpeg. > > I mean more in terms of ABI, and having to have cargo install specific > versions of the Rust compiler and so on. > > > > If we're in the habit of allowing other languages I'd be in favor of > > > allowing C++, so that we can make use of the STL containers rather than > > > rolling our own. > > > > Yikes. Rust is actually way saner for type-generic programming than C++. > > No doubt, but STL is still miles better than rolling our own > containers. > > Anyway, rather than shoehorning Rust into this codebase it might make > more sense to contribute to NihAV instead. But only if it has a sane > parsing framework That misses the point. FFmpeg should support a "safer" language than C because for some modules its the better choice. The same way linux benefits from rust. Similarly putting rust code in a different project than linux doesnt help linux. thx [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB No great genius has ever existed without some touch of madness. -- Aristotle [-- Attachment #1.2: signature.asc --] [-- Type: application/pgp-signature, Size: 195 bytes --] [-- Attachment #2: Type: text/plain, Size: 251 bytes --] _______________________________________________ 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:[~2025-02-23 21:51 UTC|newest] Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top 2025-02-20 13:06 Leandro Santiago 2025-02-20 16:20 ` Leandro Santiago 2025-02-20 22:49 ` Michael Niedermayer 2025-02-21 7:56 ` Leandro Santiago 2025-02-21 9:01 ` Tomas Härdin 2025-02-21 9:21 ` Soft Works 2025-02-21 13:21 ` Michael Niedermayer 2025-02-21 14:30 ` Soft Works 2025-02-21 14:53 ` Kieran Kunhya via ffmpeg-devel 2025-02-21 15:02 ` Soft Works 2025-02-21 19:27 ` Kieran Kunhya via ffmpeg-devel 2025-02-21 20:10 ` Soft Works 2025-02-26 13:50 ` Tomas Härdin 2025-02-26 14:18 ` Zhao Zhili 2025-02-26 15:32 ` Rémi Denis-Courmont 2025-02-26 16:03 ` Zhao Zhili 2025-02-26 16:25 ` martin schitter 2025-02-26 14:07 ` Nicolas George 2025-02-26 16:35 ` Soft Works 2025-02-21 16:39 ` Stephen Hutchinson 2025-02-26 14:25 ` Vittorio Giovara 2025-02-21 13:18 ` Lynne 2025-02-21 13:44 ` Kieran Kunhya via ffmpeg-devel 2025-02-21 18:02 ` Tomas Härdin 2025-02-22 12:57 ` Rémi Denis-Courmont 2025-02-23 21:30 ` Tomas Härdin 2025-02-23 21:51 ` Michael Niedermayer [this message] 2025-02-26 14:11 ` Tomas Härdin 2025-02-24 14:51 ` Rémi Denis-Courmont 2025-02-26 14:34 ` Tomas Härdin 2025-02-26 15:13 ` Leandro Santiago 2025-02-22 12:49 ` Rémi Denis-Courmont
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=20250223215144.GS4991@pb2 \ --to=michael@niedermayer.cc \ --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