Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Nicolas George <george@nsup.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 0/3] avutil/dict2: Add AVDictionary2 with hash-based lookup
Date: Mon, 14 Apr 2025 13:02:04 +0200
Message-ID: <Z_zrLLO1fUUZxDAI@phare.normalesup.org> (raw)
In-Reply-To: <pull.64.ffstaging.FFmpeg.1744470718.ffmpegagent@gmail.com>

ffmpegagent (HE12025-04-12):
> This whole patchset has been antirely authored by AI, wich means that I
> haven't written a single line of code.

You have got to be kidding. And not just because you waste everybody's
time submitting a series of bullshit code, but by the fact that you did
it in the first place, whether AI or yourself.

Please realize that Michael and I have barely begun to discuss the
qualitative enhancements we could get from a rewrite of the dictionary
API. And after just a few hours, you submit a series that implements…
none of them.

Coding is the easiest part of developing. It comes at the end of a long
maturation period. People can get to coding right away like you did when
they are dutifully executing the orders of whoever did the thinking
first, or when they do a school project that the teacher estimated was
doable, but certainly not when doing non-trivial things on an elite
project like FFmpeg, and even less when trying for a public API where
mistakes bite us for years.

Also, to answer a question in another mail, in case you have not figured
out by yourself:

> I'm not sure whether there are many usages of AVDictionary where stack
> allocation would be feasible or advantageous over the current way of
> "lazy init on first use", no?

I dare say that the ability to create the dictionary for avcodec_open2()
or for the title/artist/album of an audio file without dynamic
allocation and error checks is important. I will go as far as saying
that it is orders of magnitude more important than the asymptotic
performance.

As of feasibility, it looks to me like an easy task.

I would like to give the friendly advice to learn to walk before
annoying people who are talking about the best way to run a marathon (a
real one, in full armor with Persians on the heels), but in this day and
age that would cause half a dozen people to mail the community
committee, so please read this as just the expression on my own
frustration in the face of what I perceive as clueless comments in
serious discussions.

-- 
  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".

  parent reply	other threads:[~2025-04-14 11:02 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-12 15:11 ffmpegagent
2025-04-12 15:11 ` [FFmpeg-devel] [PATCH 1/3] " softworkz
2025-04-16 21:24   ` Michael Niedermayer
2025-04-16 22:38     ` softworkz .
2025-04-12 15:11 ` [FFmpeg-devel] [PATCH 2/3] doc/dict2: Add doc and api change for AVDictionary2 softworkz
2025-04-16 21:48   ` Michael Niedermayer
2025-04-16 22:43     ` softworkz .
2025-04-16 23:15     ` softworkz .
2025-04-16 23:40       ` Michael Niedermayer
2025-04-17 22:38         ` softworkz .
2025-04-19  2:28           ` Michael Niedermayer
2025-04-19 13:43             ` softworkz .
2025-04-20 20:37               ` Michael Niedermayer
2025-04-12 15:11 ` [FFmpeg-devel] [PATCH 3/3] tests/dict2: Add tests and benchmark " softworkz
2025-04-14 11:02 ` Nicolas George [this message]
2025-04-14 11:50   ` [FFmpeg-devel] [PATCH 0/3] avutil/dict2: Add AVDictionary2 with hash-based lookup softworkz .
2025-04-14 13:21   ` softworkz .

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=Z_zrLLO1fUUZxDAI@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