The thing is: there are color spaces, correct filtering etc, etc.

Sure you can do a Photoshop clone as in "Ps in 1990" if you just ask an LLM because then (and for years after) Ps itself got all this stuff wrong and people used it, professionally nevertheless.

But getting these things right requires, as-always, in-depth understanding of the theory behind it or the LLMs will gladly omit those parts.

Not least because the majority of OSS code dealing with those things gets it subtly wrong. And they've been trained on that.

A good start is btw. to ask your agent of choice to copy all theory/basics from OpenImageIO.

How do I know? I'm maintaining a closed-source, heavily LLM-assisted Rust crate that is the backbone of all image processing we do at my employer (kringers fossed it will be OSS eventually).

The amount of subtly-wrong- bites-you-eventually bugs I fixed (or had an agent fix, rather), despite tight specs and good tests, over the last 10 months, is ... noteworthy.

That said, for a lot of users it probably doesn't matter if interpolating between red and green means getting a muddy brown or that you get subtely wrong colors when you downsample and some (or quite a bit ) of aliasing when you do so more than 2× etc.

But while a lot of people want to prompt a clone of app X and an unexpected many also seem to have the patience for it: few have the background to get sth. out of that endeavour that will be genuinely useful in the end.

The CAD/parametric 3D modeling segment is another category I'm watching closely where a lot of people have the same issue w/o (yet) realizing.

And ofc, there are always exceptions where seemingly someone is behind the project who actually do know what they're doing. :)