Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

The UI is absolutely horrendous and despite decades of opportunity to fix it, there’s been zero attempt.

Blender has made some big UI gains. I used it a long time ago, and the hidden menus and backwards control scheme made it unusable for anyone with basic computing knowledge (right click was select? Insanity) and doubly so for anyone with 3D knowledge. They revamped it a few years back and it’s usable now. I went from a blender hater to happily dropping paid 3D software and preaching about how good blender is.

Companies could throw money at gimp. But that doesn’t mean it’ll ever have a control scheme that’s usable to the 99.9% of people with prior digital art experience who go in expecting something similar to 99.999% of other software, only to find it’s completely backwards.

Literally just putting aside all other development plans and going all in for a year on making the UI usable would launch the project to success.

And comments like this always get a “well, it’s open source so you could fix it yourself if it’s that bad!” I could and so could others. But there’s usable software out there, and instead of dedicating loads of time to trying to fix a decades-old mess, we’d all rather just use a better product even if it costs money and get to work, or make something different from the ground up.



How much of this is just personal opinion rather than just canon?

I love the GIMP, use it all the time, find it super-intuitive, and last time I had to use Photoshop I felt like a fresh vim user who couldnt wait to figure out how to get the hell out of there.


I'm not the original commenter, and I agree it's opinion, but it's definitely one shared by every artist and designer I've ever spoken with. The only people I know who use GIMP are engineers and devs - either folk who are die-hard OSS supporters, or people who need to do a quick image adjustment and can't be bothered Googling the ImageMagick incantation for it. Not a sign of a healthy, competitive graphics suite.

I suspect if you surveyed 1000 art professionals, you'd get very few who like or use GIMP. You're going to get a very different result with something like Blender and 3D designers though, which really should make the GIMP devs pause and think what it is that Blender does well that GIMP doesn't.


It's probably personal opinion. I'm not a photo editor, I have never used Photoshop so that has not introduced bias.

But I have found Gimp to be wildly inconsistent in the UI. I never remember how to draw a circle, for example, when I just want to add something to a screenshot because you have to use the circle cut tool and then choose a different option which I never remember because it is unintuitive. Yet its easy to have a paintbrush that draws one of those texture patterns that I can't imagine anyone ever using.

As such I then don't use it.


For drawing shapes I tend to just use Inkscape.


Yes, either Inkscape or Krita depending on the task.

There just isn't a task that Gimp fits.


The fact it’s been struggling to get widespread support for decades and there’s always someone complaining about the UI is a sign.

Most people don’t even think about photoshop UI. Same with Microsoft paint: users can get in and start figuring out what they want to do just by clicking around.


> The fact it’s been struggling to get widespread support for decades

There's hundreds of thousands downloads every month. I'm sure you have better facts at your disposal and will share them easily.


I think it does get widespread support.


I've used GIMP sparingly but the tools pane/window gets lost, it's a clumsy interface. Krita is nice (except GIMP has some nice GNOME-ish human interface touches that are better.)


Well, GIMP has been one window for a while. The tool panes aren't separate windows anymore.


I can't explain how but my tools pane was lost when I opened GIMP to inspect it during my previous comment (not visible and Tools menu -> show tools did not make it show up). Now, resetting tools window locations (in settings) did fix it. But it explains my confusion and exasperation the last few times using GIMP. (version 2.10.x)


> The UI is absolutely horrendous and despite decades of opportunity to fix it, there’s been zero attempt.

I'm afraid you are dismissing quite a lot of work to improve the UX/UI.

Could more be done? Absolutely! Was there zero attempt? Not really, no.


Honestly, if there have been decades of efforts and it’s still this bad, that’s even less motivation to give them money.

It’s like: if you’re a large manufacturer, would you prefer investing in a city where government officials pocket the cash and roads don’t exist but with handwavy excuses that something might improve with a little more cash, or invest literally anywhere else where the roads improve every year and things are getting cleaner?

Gimp seems to be spinning its tires for infinity. I’ve tried it once a year or so for 15 years. It hasn’t changed much. It’s incredible. Almost no company is going to throw them cash and it’s obvious why.


Your analogy falls short for a very predictable reason. There are exactly zero paid developers in the GIMP project.

The right kind of an analogy would be an investor stumbling upon a tiny community of developers that has been serving hundreds of thousands of users for the past 25+ years without pay.


I am pretty sure they would welcome your pull request.


Being able to open a PR and getting accepted to be merged are 2 totally different things.

IMO, one of the core reasons why UI/UX in open source applications (that aren't backed or actively contributed by dedicated staff in big companies that keeps them on a salary for the sole purpose of contributing) is because it's more widely accepted for programmers to contribute to open source than UI/UX designers.

In this case the best one can do is design mockups, but then who implements it? Who even has to be convinced that the mockup is a step forward or backwards, the moment every design decision is treated as having the same value as the next one, on the grounds of "it's just an opinion"?

My point is, we don't lack programmers/developers we lack UI/UX people willing to contribute, and we also lack the former to actually listen to what they have these people to say instead of dismissing their suggestions as "not data driven enough", "too opinionated" etc.


There’s a certain section of open source devs who fight tooth-and-nail against better UX as they see any attempt at making a software easier to use as ‘dumbing things down’.

It’s why as a UX designer I don’t contribute to open source projects any more as the fight just isn’t worth it.

GIMP is peak that attitude. It could be a top-quality mainstream open source image editor if they wanted it to, but they don’t.

Photopea is the work of one guy, Affinity Photo was made by a small team, so it’s clear it’s not manpower but attitude.

They’ve got things just how they like it and the last thing they want is to make things easier and have a bunch of n00bs running around and spoiling things, thank you very much.


> There’s a certain section of open source devs who fight tooth-and-nail against better UX... GIMP is peak that attitude.

Except the GIMP team worked with a UX architect for several years. That's how you got single-window mode, convenient rectangular/ellipse selection and cropping tool, polygonal selection tool built into lasso, the unified transform tool, and more.

And even after Peter (the UX guy) departed, the team still made a bunch of UX improvements (and continues making them, time-permitting).

> Affinity Photo was made by a small team, so it’s clear it’s not manpower but attitude.

Serif Ltd. is 200 to 500 employees. They have paid developers working full time. They had the funds to start from scratch and build on their previous experience creating similar applications.


Well, your argument inspires some thought... if one guy made Photopea, why don't a couple of FLOSS devs just copy it? (as a separate project, not as part of GIMP)


Starting from scratch usually sounds like a great idea. You don't have to deal with legacies and workarounds, what's not to like about that? :) So I get it why people think it's best to start GIMP anew. I also get it why people are reluctant to do so. While you are working on something new, you also typically don't have a working program for years. And when they already have software that works, that means maintaining two code bases at once.

In case of GIMP, the existing team is already stretched thin and has to deal with too many reports and requests to handle. In the past 4 years, the amount of reports in the issue tracker more than doubled, but the team hasn't grown accordingly. I don't think it's realistic to expect that the team would be able to maintain the current code base while starting anew. If the current progress is already commonly referred to as glacial, what do you think will happen if they start reimplementing GIMP from scratch?

And I get it why you are referring to Photopea here. I think Photopea is a formidable effort. But it's been under development for 10 years already. That's quite a long time. And Ivan didn't have another image editor to maintain while working on that project. AFAIK, he originally intended the write a web app to merely open and show a PSD file in the browser. That's a quite different development trajectory.


Mentioned that in my first comment.

There’s perfectly good software out there. I’d rather get work done and use that, than spend forever trying to make sense of some mess of an ancient project’s code and trying to fix it. There are even free projects with usable UI that would be a better use of time if I were to want to contribute to something. Krita’s been mentioned here a few times and it seems to have a brighter future.


> Companies could throw money at gimp. But that doesn’t mean it’ll ever have a control scheme that’s usable to the 99.9% of people with prior digital art experience who go in expecting something similar to 99.999% of other software, only to find it’s completely backwards.

For what it's worth, GIMP does indeed have about a million dollars sitting in their donation account. So money isn't their issue, project management is.


I'd say Photoshop UI is nothing exemplary. So why should Gimp not emulating it be a complain?

Infact I find the MDI interface to be quite ergonomic.


Nobody complained that GIMP isn't emulating photoshop.


I believe it is intentionally gimped because they are not allowed to make the UX too close to Photoshop(which, unfortunately happens to have the most intuitive / comfortable interface for photo editing) or else they would be sued by Adobe. Blame the horrendous interface on Adobe and their aggressive enforcement of software patents.


Nonsense. You can 100% copy ux of a product. There are many mac apps that closely replicate Photoshop (affinity, pixelmator, acorn)and none of them were sued by Adobe.

Also i think Photoshop is intuitive mainly because everybody is so used to it. Gimp just has very bad ux because they cant colectivelly agree and unify the ux. If the ux was very different but very good it might be even advantage but now its lot worse PS.


Flash 4 had a very nice interface full of palettes. Flash 5 dropped them all in favor of a "smart" inspector that never showed me what I wanted to see without a couple of extra clicks and a half-second wait. This was about half of why I dropped out of the animation industry, it was a complete flow-killer.

This happened because Adobe sued Macromedia over palettes.

Annoyingly enough, the interface has not substantially changed in the intervening years despite Adobe eating MM.


As an occasional user of Gimp, Photoshop's ux is anything but intuitive. The same for Krita.

I guess they are only intuitive if you use a graphics tablet?


But what about other editors with similar UX? Do Krita/PaintShopPro ever got hit by spurious patent claim?


I seem to remember there was a 3D editor, Moonlight Atelier, allegedly killed by lawyers for similarity to... SoftImage?


Maybe. But I asked for proof that Photoshop has any patents for its UX. So far, no proofs.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: