Gimp Source Code | Hacker News Reader

Gimp Source Code

gitlab.gnome.org

24 pointsroschdal19 comments

Despite Linux, llvm and Blender proving that open source can beat closed source, GIMP has failed for a very long time. If Microsoft sold something like GIMP, we've never hear the end of criticisms.

I'm not good enough to fix it, but I hope one day a team of great programmers simply restart from scratch. If they simply copied Affinity's or Photoshop's UI and core functionality, we'd have a winner.

Many years ago I spent quite some time getting used to Gimp and did some designing on it, etc. I also wrote a tutorial for it to create some torn paper effect.

I say all this to give some context to the following: GIMP is just not great software. It is super unintuitive and when you don't use it for a while, you totally forget how to use it to select things, put them on layers, etc.

I use Pixelmator on Mac. I bought it years ago and haven't regretted it. It is getting better and better of the years, the UI is great. When I use linux I miss Pixelmator more than I do Photoshop. So if someone were to create a Pixelmator-inspired editor for linux, that would be great.

The unfortunate part is gimp is intensely useful software with many amazing features...buried under such an awkward interface.

I used it today for doing a color range selection to get an estimate for parameters to use in image magick. It had the easiest dynamic visualization of the matte for the selected range as I was selecting. It did exactly what I needed, very well.

I also tested out krita and nuke. Was easier in gimp.

But gimp is still the tool of last resort as it is just so painful to use. I wish there was a more positive engagement between the graphics community and the gimp devs. It feels very combative and negative compared with tools like krita and blender.

> Despite Linux, llvm and Blender proving that open source can beat closed source, GIMP has failed for a very long time.

As a GIMP / Inkscape user who hasn't used photoshop / illustrator, what is so much better about Adobe's offerings?

I've used GIMP and Photoshop for a very long time (close to 30 years).

In ~1998, GIMP was not quite as good as Photoshop 5 and was more awkward to use, but you could see how it could close the gap. It had impressive underlying tech that could handle large images on computers at the time. There was an expansive library of weird and neat plug-ins and scripts. It felt like we were at the start of a great shift in which OSS software would "catch up" and eventually replace desktop power tools, just as Linux had done with web servers. It was... the year of Linux on the Desktop!

By ~2005, GIMP was starting to really catch up to where Photoshop was in 1998, but Photoshop had added lots of quality of line features like adjustment layers and layer effects, way better text rendering, and amazing new features like spot healing brushes, vanishing point warping, etc. The gap was widening. But GIMP still did all the core stuff, and Photoshop was annoying users by shoving Adobe Bridge down their throat, etc. So people were still hopeful for a replacement.

By ~2012, GIMP was adding.. an awkward single window mode? It lacked tons of by-now-basic features that made it totally impractical for professional use. Photoshop, meanwhile, was adding amazing time-saving features like Content-Aware Patch and Move that seemed "magic" at the time. The tech gap was widening, but Adobe was also pushing subscriptions down users' throats, which was very unpopular, so GIMP still had a chance to make a come back.

By ~2018, GIMP was finally adding.. basic CMYK support for printing, something which literally no one uses GIMP for professionally and was a dying need? Meanwhile, Photoshop was demoing an AI object selection tool that could magically select objects without needing to trace them, which came out in 2019. Using GIMP felt like using software from a decade previous.

The last 5 years have been the worst for GIMP. Photoshop has been improving at an astonishing rate. Now it's literally what photo editing looked like in 90's movies - you just open an image, click "select object" and it perfectly selects it, and lets you move/drag/add elements with AI, etc. You can do edits in seconds now that used to take hours, and the results are really good.

None of this is a complaint about GIMP or all the people who contributed to it. It's impossible for a few volunteers to complete with infinite money and hundreds of full-time employees. But Photoshop and GIMP are no longer in the same league. And Adobe knows this, which is why it can get away with punitive subscription-only pricing.

It used to lack non-destructive editing ("adjustment layers" in Photoshop parlance) until recently, it's a core foundation of editing workflows for designers and photographers, it lets you layer transformations of over immutable rasters. This was in Photoshop since 2005.

It has been a very long time since I tried GIMP (>15 years) to remember everything I found wanting, but as I recall, GIMP lacks both macros and batch editing, the former letting you record a set of actions to a hotkey so you don't have to repeat them yourself all the time, and the latter letting you apply a set of actions to hundreds or thousands of images at once. I would literally have to spend hundreds of hours to do things in GIMP that can be done with no effort in Photoshop, to the point where it would actually be easier to just program something myself from scratch than it would be to use GIMP, if Photoshop didn't exist.

I see that GIMP has since gotten a UI revamp, but the multiple window UI from the time I used it was also unbearably bad and one of the main things that sticks out in my memory.

Have you looked into script-fu? It would probably be a very steep learning curve.. BUT there is an opportunity to do something impossible 10 years ago, and that is to use AI and an external application. BATCH-FU is one such attempt but it seems to be a 'select action from a menu' thing.

But Gimp developers: implementing batch in one go is a big ask I know. But a great first step might be to create a channel in Gimp where correct script-fu is emitted for operations in progress. Being able to connect to that from outside would allow 3rd party projects to assemble "record by doing" macros that could be turned into Photoshop-like batch capability.

For batch operations on GIMP 3, I've heard great things about Batcher: https://kamilburda.github.io/batcher/

Macros are on the roadmap (https://developer.gimp.org/core/roadmap/#macros-script-recor...), and in fact we did a lot of prepwork for them during 3.0's development (internally, several features like filters and plug-ins now have configs that store settings, which will be used by macros in the future to repeat operations).

I've used [batch editing in GIMP before](https://github.com/alessandrofrancesconi/gimp-plugin-bimp), to resize a folder of images, so the feature is there. Granted it is a plugin, not a built-in feature.

I do agree though, even the revamped UI does not have a great look and feel, but I'm used to it so I don't mind.

Not entirely sure about macros, but batch editing is possible with scripts/plugins.

The multiple window thing is also a toggle setting.

I would guess you don't need to start from scratch, just take the functionality, fork and put a Photoshop-like UI on top of it. That would already be so much better.

I disagree, on both levels.

The application is perfectly fine for my needs and I'm ok with the ui.

But if you want something else, you can change that.

So grab the source code, try to get it to compile and run, and start making changes.

You have the freedom to do so. Use it. It doesn't matter that you're not great. Just do. No need to wait for others.

As an avid GIMPer for ~12 years now, I hate the UI. It's only fine because I've struggled through it for so long and now I know where and how things are.

But it's really poorly designed and outdated. I completely understand and sympathize with anyone trying to use GIMP for the first time.

Correct, I prefer inkscape and inkpot projects. Don’t use gimp.

I’m still waiting to be able to move 2 layers at once in GIMP

No need to wait! In GIMP 3.0, you can shift-click multiple layers in the layers dockable, then drag them around on the canvas with the Move tool.

That's... cool, I guess?

Somebody posted 'Adobe Photoshop 1.0 Source Code (1990)' recently so I think this post is some kind of smartass response to that.

Reply on news.ycombinator.com