> Would programmers listen to an artists opinion on programming languages and IDEs? Of course not.
I'll address that question in just a second, but as far as I can tell, the makers of GIMP have failed to listen to anybody about how that name turns people off and it's failed to gain acceptance because it's got such a terrible name. Ow heartbreaking to see such hard work wasted because horsecocks and panty-dropper, or other equally bad names could have been chosen instead. As far as listening to artists opinions, where do you think easier to use languages like Python or Ruby came from? By listening to curmudgeons that C syntax is totally fine, pointers are easy, it's fun to lose hours looking for a semicolon, and people like the author of "Real programmers use Pascal", so no need to make any changes? Or were there people, some of whom make art, who said, this crap is too confusing, and easier to use programming languages and IDEs came along? The ethos that everyone should be able to program comes hand in hand with listening to users, no matter what their day job. Programmers universally write for two classes of people. Themselves, and others. Talking to users and getting feedback (now that LLMs can write the code, but also before) is job #1 for a programmer. In order to do a good job, before you write a single line of code, you gotta find your users and see how they live, before you can write software that helps them. Find me a software project that didn't engage with its users and I'll find you software that has failed to gain wider acceptance. Like, say, Gim Paint, as I call it, since the name Gimp is such trash.
Would programmers listen to an artists opinion on programming languages and IDEs? Of course not.
The opinions themselves may be valid as relative to the individual but they’re not scalable beyond that.