GIMP and its UI are the only material here, what are you talking about? These are pain points about GIMP that multiple people have brought up every time GIMP has been mentioned online for decades.
I say this as someone who has used GIMP for two decades now. It was the first real image editor I used, so the UI/UX is fine to me, but it's clearly a problem.
GIMP is steadfast about the name, but has been slowly incorporating UI/UX improvements since its existence. (Single window mode, canvas rotation, more consistent UI on Macs with 3.0, high DPI support, etc.) GIMP doesn't have raw support yet, but it does have high bitdepth support (both integer and floating point).
The whole point of GIMPShop and PhotoGIMP are to address these pain points.
Photoshop's interface is getting worse [1] and everyone hates Adobe, so there's a great opportunity for a tool like GIMP to step up and become the default alternative. It's got a lot of features, it's been around for a long time and has reasonable name recognition (for better or worse).
However, unless they do a Blender and make a sustained effort to improve the UI, understand what people want and how it fits into professional workflows, it's never going to happen.
The attitude seems to be: If you don't like it, fuck you. I think they're genuinely happy with how things are. The inscrutable UI and off-putting name are features not bugs, keeping away the sort of people they don't want.
We then discuss and test with the reporter and volunteer designers, and try to implement once some consensus has been reached. We welcome feedback from more users, so feel free to contribute your thoughts and design/workflow issues!
I believe it's a step up from "design by whichever developer implemented a particular feature", which was the norm. :)
More seriously, we're trying to attract more designers and design feedback, just like we do for coding. We're also trying to document UX standards (see https://developer.gimp.org/core/ for early work) so there'll be a consistent experience as new developers join and features are added.
The company absolutely failed the test. If they're not using industry standard tools then it's a sign they don't take the role seriously. That would be a huge red flag to me.
It's like applying to be developer and being told to use Microsoft FrontPage. It's doable, but raises serious questions about the professionalism of the organisation.
Pipedream was an odd bit of software, but the article is a bad take on RiscOS itself.
It was way ahead of Windows at the time and even Mac OS didn’t really catch up until System 8.
I was astonished when going to friends’ houses at how backward and clunky their IBM compatibles with 5” drives seemed in comparison.
From an interface side, what’s interesting (and alluded to in the article) is how file-focused RiscOS is. There wasn’t the concept of an in-app file picker. If you wanted to open a file, you navigated to its location in the file system. To save, you dragged the icon to the folder you wanted to put it.
Programs being folders was useful for mischief. Most people never noticed the ! in the filename, so I’d amuse myself by turning classmates’ document folders into applications that would run a script when clicked. I’d fire scary error messages, load full-screen images or mess with the system settings.
• A visual moodboard and notes app that uses local models to link and surface content, a bit like an AI powered Memex.
• A new UI design tool for Mac/iOS with deep support for design systems and AI agents.
• A CMS and static site generator that runs entirely in the browser. Download the site as a zip or publish directly to GitHub/Netlify.
https://github.com/sparktype-project/sparktype
reply