From: Nicolas George <george@nsup.org> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH v2] avformat: add Software Defined Radio support Date: Thu, 29 Jun 2023 09:14:49 +0200 Message-ID: <ZJ0vafCoilAnFMO9@phare.normalesup.org> (raw) In-Reply-To: <f3c19fb940a7923338373ae5bbec3daef9e1fe89.camel@haerdin.se> Tomas Härdin (12023-06-29): > This is very revealing. Indeed. > The reason why XML parsing shouldn't be > implemented in FFmpeg isn't just because it is difficult but because: > > * it is out of scope It is necessary. > * it is technical debt > * shitty parsing is the cause of the vast majority of CVEs > > It speaks of an inability to make sane architectural decisions, of not > seperating concerns and of preferring cowboy coding over sane decisions > with respect to the entire free software ecosystem. Thank you for illustrating my words with your inability to consider that (1) we do not need a complete parser (2) the things that make parsing XML hard are precisely the things we do not need and (3) if you consider writing such a XML parser is way too hard, it speaks more of your skills in that area than anything else. > Are you implying that API and ABI stability are not important? Precisely. Nothing is “important” in absolute?. Things are only important with regard to a goal. My goal is to have fun, and for that goal, API and ABI stability are not important. To have fun, I still need the project to exist, so I will spend time on these issues, that is all. API and ABI stability are important if you want to be of service. I do not want to be of service. Maybe you want FFmpeg to be of service, you seem to. Well, let me tell you this: if you want to force me to not have fun and spend effort on things you think are important instead, go fork yourself. -- 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-06-29 7:15 UTC|newest] Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-18 22:28 Michael Niedermayer 2023-06-22 13:43 ` Michael Niedermayer 2023-06-22 13:55 ` James Almer 2023-06-22 15:05 ` Michael Niedermayer 2023-06-22 15:10 ` James Almer 2023-06-22 16:26 ` Michael Niedermayer 2023-06-22 16:42 ` James Almer 2023-06-22 22:00 ` Michael Niedermayer 2023-06-23 2:34 ` Kieran Kunhya 2023-06-23 11:17 ` Michael Niedermayer 2023-06-23 11:36 ` Kieran Kunhya 2023-06-23 16:37 ` Rémi Denis-Courmont 2023-06-23 18:12 ` Michael Niedermayer 2023-06-23 18:17 ` Paul B Mahol 2023-06-23 18:56 ` Michael Niedermayer 2023-06-23 19:10 ` Paul B Mahol 2023-06-23 19:16 ` James Almer 2023-06-24 20:27 ` Rémi Denis-Courmont 2023-06-24 21:03 ` Tomas Härdin 2023-06-25 13:53 ` Michael Niedermayer 2023-06-25 14:25 ` Michael Niedermayer 2023-06-24 22:19 ` Nicolas George 2023-06-25 14:10 ` Michael Niedermayer 2023-06-27 19:09 ` Rémi Denis-Courmont 2023-06-28 22:15 ` Tomas Härdin 2023-06-29 7:14 ` Nicolas George [this message] 2023-06-29 9:46 ` Jean-Baptiste Kempf 2023-06-30 21:51 ` Tomas Härdin 2023-07-02 8:11 ` Michael Niedermayer 2023-07-02 9:34 ` Nicolas George 2023-07-02 9:54 ` Tomas Härdin 2023-07-02 9:56 ` Nicolas George 2023-06-23 20:10 ` Tomas Härdin 2023-06-23 21:18 ` Michael Niedermayer 2023-06-24 9:51 ` Tomas Härdin 2023-06-24 21:01 ` Michael Niedermayer 2023-06-24 22:01 ` Tomas Härdin 2023-06-25 9:54 ` Michael Niedermayer 2023-06-27 9:00 ` Tomas Härdin 2023-06-27 10:57 ` Nicolas George 2023-06-27 17:07 ` Tomas Härdin 2023-06-27 17:11 ` Nicolas George 2023-06-25 10:23 ` Kieran Kunhya
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=ZJ0vafCoilAnFMO9@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