If GIMP were to implement it, they'd probably have to go the same route as Krita and either spin up or call out to a running instance of Automatic1111 or ComfyUI.
https://github.com/Acly/krita-ai-diffusion
MCP would be cool, but it would be significantly harder than Blender which can represent the "world" as a formal set of expressions. MCP for GIMP would be dealing with layers of rasterized data which would mean integrating with YOLO/LLava/etc in order to make sense of it. It would be neat, but it'd be a daunting integration and potentially VERY VERY slow.
And I resent the fact that I'm expected to pay that price when I'm not the one who was losing projects.
And as I said, carrying out the instruction but then telling me that I should be using Export instead would be acceptable. Refusing to carry out the instruction, even though the software has identified and understood the instruction just because I failed to say 'Simon Says' is not acceptable.
(Hi, by the way! I think you did some translations for PhotoPrint and CMYKTool some years back?)
Yes, I understand the frustration. The team didn't come up with anything better although maybe they could. I think another suggestion in this thread could very well be posted to GIMP's issue tracker.
> a) have a working mental model of software functioning, so they reason about interfaces differently
You're 100% correct, they do reason about interfaces differently, and thus have wants and needs which are different from those of non-technical users. Those wants and needs are not met by mainstream software, but are met in some OSS software, so it should come as no surprise that such types want to defend that software against the incursion of those who want to make it just like the mainstream offerings!
Like you I have a slightly different perspective here, having been a hobbyist software developer for some years, but having worked in print and design as a day job.
But I still bemoan such things as the awful keyboard handling of the current GTK file dialog, when compared with the old GTK1.2 file dialog. The old one was truly hideous to look at, but handled filtering files by keystroke far better than any current file dialog.
Also 2004: HOW DO I RECOVER LAYERS FROM JPEG?
2024: STOP TELLING ME YOU ONLY SAVE TO XCF AND I NEED TO EXPORT TO JPEG!
Also 2024: crickets
I'm not kidding you. That is exactly what I've been witnessing all these years. Project loss complaints went from daily routine to almost zero. But there's a price to pay.
I’d been learning CAD with Ondsel, and have printed off half-a-dozen of my models to help around the house.
If this comment finds its way to the team, I just want to say thanks.
The topo naming fix and the assembly workbench were enormous contributions to the community that will be with us always.
But I really believed in Ondsel’s vision for an online repo for 3d models.
I imagine lots of complaints are either outdated, or by people who are used to different CAD systems and expect them to work exactly the same.
I've tried and worked with Catia, solidworks, and fusion 360, and I can easily complain about each of those for being confusing.