Posted by ibobev 3 days ago
> [Øyvind] is the maintainer of GEGL and babl, the color engines of GIMP. His work was instrumental in (among many other things) the long-waited non-destructive filters implemented in GIMP 3.0
The interview is about Pippin's background (fine arts) and current (as of the time of the interview) work, and in some details about the graphics engine underneath GIMP (GEGL).
FWIW, it doesn't touch on the UI/UX side at all. So even you Photoshop lovers may find it interesting :)
>In my honest opinion, GIMP is a horrific piece of software.
Both are absolutely true!
GIMP has been, for many years, the best free graphics software available. At the same time, it's so horribly anti-user (and anti-usability) that if it wasn't free software, the company behind it would have gone bankrupt a long time ago.
I have used far worse software from commercial outfits. You would not believe how much aerospace and specialized CAD stuff still uses Motif and doesn't support scroll wheels or extra mouse buttons.
For those of you who daily drive GIMP, well you'll be up to speed quickly. For those of us that use it once a month or so, for a day, it quickly becomes exceptionally annoying.
I'm happy if the UI isn't the best. I frankly don't care what the software looks like, or if the GUI is purdy. I just want it to work, work well, and frankly that menu items don't magically disappear, get merged into other sub-menus, or that now you can suddenly close a tool, and never ever get it back without finding some obscure menu item to re-activate it.
And if you use GIMP frequently, and are about to say "But, that's easy, you just..." then you're not a casual user.
There are more casual users than you think.
(this goes right up there with devs who change config options in files from option= to Option=, and configs= to config=.
I mean, leave it alone. Forever.
"Updated config options to bring them inline with StudlyCaps" or whatever turns my day into a ragefest filled anxiety attack on upgrade.
"Changed all config names to US English from British spelling." What?! OK b112, you now have to deal.
I don't want to deal. I want to eat doritos.)
We try to be respectful of existing users (and again, we get lots of complaints that doing so "holds GIMP back"). If you have some examples of massive changes you've dealt with (and from what version to what version), I'm happy to look into them further.
[1]gave up on it 10 years ago, so don't know, maybe things changed
Imagine that you are a car hobbyist. You know your way around a wrench.
But then you step in to an F1 garage or even your local repair shop run by that one guy who inheritted his father's shop in the 50s and has thrown a tool away since the Reagan administration.
It's going to be possible for you to do everything that you know how to do, and even to learn some things along the way, but you're not going to be anywhere near as efficient as you were in your garage where the only tools you have are the ones you regularly use and you know the locations (perhaps roughly) of everything.
The same could be applied across any number of domains. Knowing your way around and ambulance isn't going to go as far as you might think it would in a surgical suite.
Knowing some python isn't going to get your pulls accepted in Canonical, Debian, etc.
Knowing your professors preffered citation methodology isn't going to gaurantee academically succesful searching of The Library of Congress or even the New York Public Library.
etc etc etc
GIMP represents nearly the totality of knowledge relating to image manipulation, and you can lay it out to perfectly match your personal knowledge and workflow, but it simply is not possible to have it automatically laid out to perfectly match everyone's workflow.
Could it be more intuitive? Perhaps, but moving things around now is liable to break the workflows of tens of thousands who have learned to use and love GIMP the way that it currently is.
For instance, having only ever used GIMP as my primary image manipulation tool, I can and do have some of the same complaints against [insert other software] that people routinely level against GIMP. The last time I tried to use Photoshop I spent more time in tutorials and help pages than doing actual image editting because Photoshop is as unfamiliar to me as GIMP is to a Photoshop user.
Of course such an effort most likeky would need to be a paid effort fulltime rather than volunteerr work.
It always felt sad to me it never reached the usablility/familiarity that Blender has.
Longterm, we have a roadmap item for an Extensions platform: https://developer.gimp.org/core/roadmap/#extensions
So basically, you could download plug-ins, themes, shortcut presets, etc, directly into GIMP. We have a lot of pieces done - we just need someone to focus on it to finish.
I’ve noticed small but consistent improvements over the years. People who complain about the UX should just go use Photoshop. It’s fine. Layers work well, retouching and filters are easy. I don’t really understand the complaints.
I’m very glad GIMP exists, and I hope it continues to make FOSS haters cope and seethe for the next 50 years. Keep whining about the name please!
"And it turns out there are a couple hundred people already who would like me to continue writing code and sharing it publicly and openly. That at least sustains me roughly on the level of unemployment benefits in European countries. And I hope that this will even slightly increase – I will not have a Silicon Valley level software developer salary, but I’ll have enough money to cover my expenses."
And I say this as somebody who rather likes the gimp.
I am confused
> This interview took place on February 4th, 2017
Not really -- It invites speculation as to why they were not published for 9 years. And, are the words spoken a decade ago still valid?
I volunteered to help with transcription, so I was given several audio recordings and started working on them. The first "resurfaced" one was Simon Budig: https://www.gimp.org/news/2025/11/01/simon-budig-interview-w...
There's about 4 more from another event which I'll be working on between coding and other things. There's definitely some material that's a bit dated (for instance, the comment about non-destructive editing), but I think it's still interesting insight into development.
I think the interview is interesting regardless if some of the details within are dated or not.