> while they 100% against using AI to generate art or game design, when you ask them about using AI tools to build software or websites the response is almost always something like "Programmers are expensive, I can't afford that. If I can use AI to cut programmers out of the process I'm going to do it."
Three things:
1. People simply don't respect programming as a creative, human endeavour. Replacing devs with AI is viewed in the same way as replacing assembly line workers with robots.
2. Somewhat informed people might know that for coding tasks, LLMs are broadly trained on code that was publicly shared to help people out on Reddit or SO or as part of open-source projects (the nuance of, say, the GPL will be lost). Whereas the art is was trained on is, broadly speaking, copywritten.
3. And, related to two: people feel great sympathy for artists, since artists generally struggle quite a bit to make a living. Whereas engineers have solid, high paying white collar jobs; thus, they're not considered entitled to any kind of sympathy or support.
I've been a professional artist, designer, and developer. Mostly a developer, and working in academia throughout the late teens meant being privy to the development of neural networks into what they've become. When I pointed out the vulnerability of developers to this technology, the "well maybe for some developers but I'm special" stance was nearly ubiquitous.
When the tech world realized their neato new invention inadvertently dropped a giant portion of the world's working artists into the toilet, they smashed that flusher before they could even say "oops." Endless justification, people saying artists were untalented and greedy and deserved to be financially ruined, with a heaping helping of "well, just 'pivot'."
And I did-- into manufacturing because I didn't see much of a future for tech industry careers. I'm lucky-- I came from a working class background so getting into a trade wasn't a total culture and environment shock. I think what this technology is going to do to job markets is a tragedy, but after all the shit I took as a working artist during this transition, I'm going to have to say "well, just pivot!" Better get in shape and toughen up-- your years of office work mean absolutely nothing when you've got to physically do something for a living. Most of the soft, maladroit, arrogant tech workers get absolutely spanked in that environment.
> 1. People simply don't respect programming as a creative, human endeavour. Replacing devs with AI is viewed in the same way as replacing assembly line workers with robots.
It is about scarcity: art is a passion; there is a perpetual oversupply of talented game designers, visual graphic artists, sculptors, magna artists, music composers, guitarists, etc...you can hire one and you usually can hire talent for cheap because...there is a lot of talent.
Programmers are (or were?) expensive because, at least in recent times, talented ones are expensive because they are rare enough.
Most of the code that was publicly available to be trained on is written by people in their spare time, not directly making any money off of it though. Personally I think if you are fine with AI used to generate code you should also be fine with it being used to generate art. That doesn't mean that I think that big companies just scraping the entire internet and training on large amount of portfolio pieces from ArtStation or people making open source projects is good either.
People don't respect the salary premium software developers have received and expect relative to other creative, human endeavors.
You lay it out perfectly in your answer, and I'll add that the entire non-tech world generally feels that if tech jobs lose their shine due to AI, its actually a welcome reversion to the mean. Software has likely depressed wage growth in many other jobs.
> People simply don't respect programming as a creative, human endeavour.
Because it's not? Programmers' ethos is having low attachment to code. People work on code together, often with complete strangers, see it modified, sliced, merged and whatever. If you rename a variable in software or refactor a module, it's still the same software.
Meanwhile for art authorship, authenticity and detail are of utter importance.
> 1. People simply don't respect programming as a creative, human endeavour. Replacing devs with AI is viewed in the same way as replacing assembly line workers with robots.
Very reminiscent of the "software factory" bullshit peddled by grifters 15 or 20 years ago.
And I think, frankly, a lot of agile practice as I've seen it in industry doesn't respect software development as a creative endeavour either.
But fundamentally I, like a lot of programmers/developers/engineers, got into software because I wanted to make things, and I suspect the way I use AI to help with software development reflects that (tight leash, creative decision-making sits with me, not the machine, etc.).
Yeah people clearly think "creatives" are a class apart from white-collar workers.
> Whereas the art is was trained on is, broadly speaking, copywritten
The overwhelmingly vast majority of the code you're talking about (basically, anything that doesn't explicitly disavow its copyright by being placed in the public domain, and there's some legal debate if that is even something that you can do proactively) is just as copyright protected as the art is.
Open Source does not mean copyright free.
"Free Software" certainly doesn't mean copyright free (the GPL only has any meaning at all because of copyright law).