Tux Paint is feckin awesome. Not even photoshop has sound effects when you use a tool.
I kind of agree. I’m not a pro but I’ve been using gimp to do little bits of editing (mostly to make slack emojis and memes) for a few years, and I constantly encounter little things that seem like they should be simple and intuitive, but are not.
I haven’t used Photoshop in over a decade, but I feel like I rarely felt the same frustration regarding basic tasks.
It’s that phenomenon where people who endured trauma to attain something expect others to also endure the trauma.
I’ve tried learning GIMP, and it sucks. I’m not saying GIMP sucks, but you have to be crazy to not see that it’s hard to learn.
Not vonly hard to learn, it lacks some really basic stuff like undestructive ediring (adjusment layers) and such.
I am using 2.99.18 (non release, unstable build). Non destructive editing has landed. You can make adjustments through the usual menus and then enable/disable the adjustment under layer effects.
Wow, that’s greate!
I’ve tried learning GIMP, and it sucks. I’m not saying GIMP sucks, but you have to be crazy to not see that it’s hard to learn.
I use GIMP for memes and here’s my two favorite tips
-
Hit the forward slash key
/to open a command palette and jump to any action -
To remove backgrounds, use a layer mask. select around the object and paint a white/black section on the layer mask. Here comes the trick: use a Gaussian filter on the layer mask to create a transition from black to white and the crop job looks a lot less choppy.
My anti-tip
- Adding text and shapes sucks and I never found a way to make it better. Export your image and finish the job in Krita, Pinta, Photopea, …
-
No, GIMP does suck.
It has the same problem as most FOSS packages that are too wide in breadth and have multiple contributors with their own hobby horses pulling in all different directions, and to this day does not actually provide a feature-complete whole, nor an interface that actually makes sense. And it’s not a matter of the workflow just being different – it categorically fails to replicate functionality that is core to its commercial competitors. Numerous other “big” productivity packages have the same problem including FreeCAD (boy does it ever), LibreOffice, etc. I say this as a staunch supporter of FreeCAD, by the way. It’s the only CAD software I use even though it’s a pain in my ass.
The shining exception to this I see is Inkscape, but it is still significantly less powerful than even early versions of CorelDraw.
For 2D graphics work these days, I hold my nose and just use Corel. I use it for work. Like, actual commercial work. That I get paid for. It is at least a lesser evil than doing business with Adobe.
And if you want to stick it to the man, it is easily pirated.
In FOSS most people can program, but only a hand full of people can design a decent UI.
There’s also two main plus one lesser issue that are less commonly discussed:
- Lack of manpower. FOSS devs often doing it as a side project on top of some other and/or a full-time job, so that even lowers one’s ability of concentrate on stuff like the UI, when you’re already working hard on fixing bugs, looking up things (which is getting harder and harder thanks to AI slop - I once managed to destroy a Linux on my Raspberry Pi while trying to adjust the path variables).
- Getting comfortable with the uncomfortable parts of your application. There are many times I haven’t noticed a a very uncomfortable part of my GUI after months of use, then I had to refactor things, which obviously took time away from other things. This also affects the users already in the userbase.
Elitism is also a factor. A lot of people like the feeling of being part of a special group, and for them, the steep learning curve is a feature, not a bug. I’ve seen Blender users being angry at the devs for “spoonfeeding” the normies, and letting in all kinds of people. Also just look at OP’s image.
I always wondered if I could contribute/volunteer to a FOSS somehow with some UIX stuff, but I don’t even know where to start. Would you just draw a concept ui for the team to work out or something?
Not that I’m great at it, but man, we gotta start somewhere, right?
This is probably common. The people that work on UI often aren’t the people who do pull requests. But I think if you want to contribute it would be best to get in touch with a maintainer on the chat of the project. Projects often have a matrix/irc/discord on the git page.
So, why do UI people not use and contribute to FOSS then? Are they all on Mac? Then go complain to them or contribute your desired UI improvements. FOSS isn’t an all you can eat buffet.
Personally, I think UI people are less idealistic and I do look down on them for that.
It’s super hard to get involved as a UI person. If you’re a developer, you can just rock up to a project and fix bugs, and if you follow the coding style they’ll probably get accepted.
If you want to successfully contribute as a UI person you have to convince a bunch of developers that you know what they should be doing better than they do. It basically never happens.
I’ve tried learning GIMP, and it sucks. I’m not saying GIMP sucks, but you have to be crazy to not see that it’s hard to learn.
“Im not saying it sucks but it does” How do you want us to take you seriously when you don’t even agree with yourself ?
They didn’t say GIMP itself sucks, they said leaning to use it sucks. Those are two different things.
I honestly think it’s unfair to judge someone for not putting significant time into learning another complex program. I’ve used Photoshop since it first existed, and it’s basically a lifetime of knowledge. A combination of things has brought me to exploring other open source solutions, but GIMP is definitely unintuitive in comparison. I’m only putting the time in because there’s literally no alternative that’s as powerful and ubiquitous an image editing solution, but I’d also be the first to jump on alternatives that would make the transition easier. It’s especially not fair to cast that judgement on professionals who don’t really have the time to invest in learning a new tool from scratch.
anyone who has ever used image editing software professionally knows gimp’s ui sucks very much.
we could have had an opensource photoshop killer if the developers werent adamant to keep the 90s workflow holding it back for so damn long.
“you are using it wrong!!” my ass.
I feel like the issue is that people expect a “Photoshop killer” to be Photoshop verbatim. Instead of focusing on making a good tool, people just constantly compare it to the commercial pack leader.
Most of the complaints I hear about GIMP are just “x isn’t like Photoshop”. I would take the complaints more seriously if any of the people voicing them could actually articulate what should be improved.
I mean, there’s something to be said about adhering to an industry standard. Of course no project has to do so if they don’t want to, but people trying to get on with their work don’t want to spend a bunch of time relearning everything. I think Blender really thrived when they loosened up a little on their ideas of what a workflow should be and gave people industry standard options out of the gate.
Whether we like it or not, GIMP isn’t going to be most people’s first experience with image manipulation. Whether they had a free PS license through school/work, had a subscription at some point, or once got it through ahem alternative means, people will be coming into GIMP with certain expectation of what the workflow should look like and will get frustrated pretty quickly.
That’s fair, but it doesn’t answer any of the questions about what should be improved. “Industry standards” is a vacuous term when the standard is defined by a singular piece of software made by one company.
Sure, GIMP isn’t Photoshop, and those familiar with Photoshop will have to re-learn things to use it. But what exactly needs to be changed? The developers have no chance of improving the program if the feedback is this generic.
we saw a similar thing with blender, everyone kept shitting their pants over blender, until studios started actually using it, and then nobody cared.
Most of the complaints are just people mad that they have to learn something. As is true for most things in life.
Blender has also undergone multiple UI changes over the years to make it more usable for new people.
this is also true
Krita is great.
I feel like Krita is more focused on digital painting, rather than image editing
I mean, what exactly does gimp or photoshop do (besides the RAW editing tools–but if you’re using those you’re already a professional) that Krita doesn’t?
I tried using Krita instead of gimp but found it hard to do color management: adjust levels, exposure, color curves and such. At the time I simply couldn’t find any dialogs to do many of those tasks.
Yeah you’re right, it’s not meant for that
Right now I’m in a bit of a bind because part of my workflow relies on exporting particular layers and layer groups as separate images. GIMP has a plugin for it, but it uses Python 2, no longer developed, and likely won’t work in GIMP 3. If Krita can do this, I’m switching immediately.
Oh I wish GIMP had a “export visible” functionality. My workaround is usually to “copy visible” and then paste to a new image.
Isn’t that what the basic “Export” does?
Looks like it can: https://superuser.com/a/1347993
I feel like it would be helpful to include the text of their post rather than just the title:
TL;DR Sorry if this is wrong group. GIMP = Epic POS. Do not use. Please recommend a decent alternative. Don’t waste your time with GIMP help because I am done.
I hope the mods or the bots don’t kill this post right away. It’s a serious and legitimate question from a UX designer with several decades of experience, who doesn’t want anyone else to suffer what I have. I didn’t know where else to post it, so I’m trying here as a first-timer. I apologize if this is not in the spirit of the group.
I quit Adobe, can’t afford the price any more (long story). I thought GIMP could replace Photoshop. But the user interface is horrible, and the app is full o’ bugs.
Here’s the straw that broke the camel’s back.
I tried to make a meme. The font selection overlay was a tiny, pathetic, hard to read joke. Not even a font selection dropdown, let alone one that provided previews with every line item like PS does. Deep breath, continue. I type “Impact”. Red text. I backspaced and typed “Im”. All I got was Impact Condensed. (Yes, I have Impact, and have used it in PS). So I picked it anyway. Then I tried to find the outline font feature. In Photoshop, it’s a simple “choose stroke” feature. GIMP? Hello?
I want to the Web to find a tutorial where it pointed out the feature. No luck. Searched again to find a workaround / hack. Mostly crap. Found one that was current and seemed decent. Followed it carefully. GIMP crashed.
While I appreciate the thoughts of anyone who may be compelled to point out a simple workaround or feature that I missed, don’t bother. This is the last of many dozens of problems I have wasted my time working around while suffering many crashes, and I already uninstalled it.
So. Recommendations?
I think it’s also worth giving the correction that there is a font selection dropdown with previews in GIMP. It’s to the left of the font input box.
I use gimp but OP isn’t wrong. Doing a stroke on text is mindless in Photoshop and very convoluted in gimp.
GIMP needs the Blender treatment honestly. Inkscape too. That would cover the vast majority of what I do art-wise.
Gimp 3 might clear some of that up we will see
I hear good things about Krita.
GIMP would be infinitely better if they just changed the name so we could talk about it around normal people without getting dirty looks
Just don’t live in an English speaking country, easy!
Also if they made it have a workflow friendly to people who are used to almost anything else
I recently started having the bug again where Gimp crashes when changing text color. Apparently related to Wayland, but I can’t change back to xorg just for gimp. Extremely frustrating as I’ve had that bug half a year ago, then it went away and now its here again.
Anyway, Krita and Photopea are pretty good replacements. Handling Text in Krita is horrible and working in a WebApp with Photopea is weird, but overall still better than crashing…
Jesus have my expectations for Linux software fallen over the years.
That has been my experience with wayland. A bug pops up then goes away in the next release of the software only to reappear later on. You can report the bug you have but it seems no one is finding the actual cause since the bug report never moves.
stuff like this is why i’m waiting a few years to move over to wayland properly.
I just don’t have the time and energy for this kind of stuff, sure X is a dinosaur, and fucking ginormous, but it also just fucking works™ and i don’t have to deal with updates, because it’s literally feature complete.
Except when X doesn’t fucking work ™ and hasn’t properly worked in literal decades. I don’t think I’ve ever managed to get rid of horizontal tearing with X. Calling X feature complete is pretty funny, but it isn’t. So many things were never fully implemented, because it’s just an impossible amount of work or would require some major rearchitecting. You don’t have to deal with updates because literally no one wants to develop it any further or even maintain it. The devs have moved on to Wayland or other things.
It’s fine if it works for you, but I’m getting tired of Linux conservatives projecting their own experiences on everyone else and declaring Wayland as “not ready yet” and handwaving all of X’s obvious problems away because they’re used to dealing with them. I’ve used Wayland as a default for all my machines for years. After a rough beginning where major features were still in development, now it works. XWayland works. Native Wayland apps work. I don’t have tearing anymore. I’m not going to pretend that that’s the universal experience, but a lot of people are using it just fine right now.
i switched to i3wm and picom, recently, initially had issues with tearing, but honestly, i just haven’t seen tearing recently, and i’m not sure why.
It’s fine if it works for you, but I’m getting tired of Linux conservatives projecting their own experiences on everyone else and declaring Wayland as “not ready yet” and handwaving all of X’s obvious problems away because they’re used to dealing with them.
valid opinion i guess, but i just stated the reason why i’m waiting a few years until moving to wayland, if i were a linux conservative i would refuse to move off of X lmao.
It’d be nice to use wayland, but from what i’ve heard and what i’ve seen it sounds like it’s going to be equally as annoying as X is, especially more so because i’m currently using nvidia, and wayland doesn’t seem to support nvidia as well as X does, just due to development focus. Currently i just don’t think the CBA is going to be significantly net positive enough to rip up my entire current install, transition from i3wm, to another one, and then start using/learning wayland, just yet.
Like yes major releases and distros are moving to wayland now, that just means they find it stable enough to start doing development on it. I’ll wait a bit and then later move over once things settle down. I have years of experience using X, and significant familiarity with it. I have none with wayland, i’d simply prefer to wait a bit.
wayland doesn’t seem to support nvidia as well as X does, just due to development focus
Ymmv with Nvidia, but that has nothing to do with development focus and everything to do with Nvidia’s refusal to use the same interfaces Intel and AMD use. Most of the way Nvidia works or doesn’t work with X or Wayland is down to Nvidia’s driver stack. Personally I’ve not had much positive experiences with Nvidia on X.
Like yes major releases and distros are moving to wayland now, that just means they find it stable enough to start doing development on it.
That happened literal years ago. The reason you’re only noticing now, might be because KDE has gotten their Wayland implementation to a reasonably stable point. Gnome has supported Wayland for some time now and other DEs probably don’t have the resources to move on from X. I don’t see the distros that are only switching over now as major contributors to any development specific to Wayland.
I don’t take issue with your preferences. Maybe you’re better off with X for now, that’s fine, but you make it sound like Wayland is just full of issues and has barely even entered some kind of pre-release state for software masochists.
Ymmv with Nvidia, but that has nothing to do with development focus and everything to do with Nvidia’s refusal to use the same interfaces Intel and AMD use. Most of the way Nvidia works or doesn’t work with X or Wayland is down to Nvidia’s driver stack. Personally I’ve not had much positive experiences with Nvidia on X.
that’s what i mean, i don’t blame wayland for it lol. I wouldn’t want to develop for nvidia on wayland either. If nvidia was open and accessible, someone somewhere, would be working on it right now, it’s just how things are.
That happened literal years ago.
it’s possible that i missed a few i’ve only been involved for about 4-5 years so far. I don’t know anything about gnome personally because i don’t use it, but it doesn’t surprise me either tbh. I know about KDE because i used it, i know about fedora because i know people who have used it. I feel like i’ve seen more talk about wayland as of recent, but that’s probably irrelevant lol.
I don’t see the distros that are only switching over now as major contributors to any development specific to Wayland.
it’s not the distros and their devs, it’s the users and their unique hardware configs. More data makes a more reliable and usable system.
I don’t take issue with your preferences. Maybe you’re better off with X for now, that’s fine, but you make it sound like Wayland is just full of issues and has barely even entered some kind of pre-release state for software masochists.
that’s not what i intended, i just said it’s the small issues that appear, and disappear with every few updates, that i don’t want to be dealing with, that’s why i no longer use KDE. I prefer my system to be a relatively consistent level of “broken” most of the time.
A lot of people don’t have significant issues with that, i believe the previous poster was rather annoyed by them, i imagine they’ll get better soon, but there will likely be hundreds, if not thousands of bugs like this, dependent on specific hardware configurations, that will crop up shortly. And then just randomly disappear, or morph into other bugs, this is the QOL hell part of development.
X is rather stable on virtue of not being updated anymore, so those aren’t really significant concerns.
Linux users try not to be Apple fanboys but replace popular Apple product with popular Linux product challenge (impossible)
To be fair, you can’t exactly ask for a GIMP replacement on r/GIMP and not expect that reaction
Sure you can.
I’ve tried using GIMP and it absolutely sucks and I wish there was a good paint.net replacement.
Something I found about a lot of open source projects is that the UI is always terrible
https://www.pinta-project.com/ based on older version of paint.net source code.
I do get, why people dislike GIMP. It has a bit of a steep learning curve. And approaches things uniquely.
But for a FOSS paint equivalent: have you tried Pinta? It’s much less complicated, and the UI isn’t too bad.
Based on the screenshots I see, it looks a lot better. I’ll give it a try, thanks!
Krita is pretty good.
Gimp isn’t perfect. But neither is Photoshop. In fact Lightroom users grizzle that Photoshop is so much harder to use than Lightroom. It’s a different animal.
I use Pinta or Paint.Net when I want a quick edit. But Gimp has the tools for serious editing. More tools, more hard to use.
Some Gimp things, yes! should be improved. And other things are being improved as we speak. And some things can be done on a photo much easier in Inkscape.
I hope the whiners donated to Gimp development? No? Then just please step back, and think for a bit. If thinking is too hard, then just take a deep breath.
Donating to GIMP will not likely make it user-friendly enough to make me use it unless absolutely forced to. I would much rather donate to Pinta or Paint.NET or something where development would actually benefit me.
Coming from Paint.NET, I first tried Photoshop and I felt its controls to be non-intuitive, so I reverted to Paint.NET.
Later, I started using GIMP and coming from someone with no experience in either of them, GIMP and Photoshop are equally non-intuitive, so whenever someone complaining about GIMP, feels like they are coming from Photoshop, I just discount their rating.
Inkscape is a vector graphics editor, which is different from GIMP.
Wow! I have been looking for gimp alternatives or specific ways of doing things on gimp, compared to photoshop and most answers have been very honest and helpful!
Even gimp development team are open for suggestions but won’t consider them before releasing version 3 that should release ‘very soon’
it’s accurate though.
The amount of PS users i see trying gimp for all of about 2 seconds and then shitting themselves when it isn’t exactly the same as PS is funny to me.
There are important technological differences i suppose, but i rarely see people complain about that.
GIMP is a monster, as is PS. There is no getting around it.
Show me how to change 1 pixel in an image. I’d actually be truthfully thankful and will consider to try to use gimp again (last time I tried the mouse didn’t position/choose the zoomed in pixels correctly).
Show me how to open an image, make a small modification, then:
(step 2) save it and close GIMP under 10 clicks.
They deliberately changed so you can’t save your modified image? I mean WTF? You have to export it with all the popups as you overwrite, hold your breath, the image that you opened and want to save!!1!.
Then trying to nag you into saving it to some unknown unused bizarre gimp extension.
It’s like they don’t want people to switch. And it’s such a shame as the soft is getting better and better all the time.
(step 2) save it and close GIMP under 10 clicks.
File -> Overwrite (2 clicks)
File -> Quit (2 clicks)
Yes I want to quit, even though I haven’t saved it as an .xpf file (1 click)
Total: 5 clicks
It’s more like File-> export->select PNG->save->select your file(that you just opened and modified)->save->yes I want to overwrite it THEN close the image in Gimp->no I don’t want to save image.xpf.
Instead of a CTRL+S
I mean sometimes you’d probably missclick too…
File > overwrite
Bind it to Ctrl+s if you want.
It only saves as an xcf project if you choose save instead of overwrite.
the fuck do you mean “it’s more like” i just reproduced those 5 steps using my copy of gimp
Not saving a project file, but the image file you just opened. Learn to read, sheesh.
like you are aware that overwriting the file you opened, as opposed to saving a project file, is what I just told you how to do in 5 clicks?
Yes, that is what those steps do
-
File > overwrite yourimage.jpeg
-
Ctrl+Q
That’s 2 mouse clicks and one keyboard shortcut.
You can even make number 1 keyboard shortcut if you want. How is that any more laborious than photoshop?
-
Then trying to nag you into saving it to some unknown unused bizarre gimp extension.
You mean saving a project file? The same way you’d save a PSD file in PS, so you can actually save all your layers and go back to make an edit? It’s been a while since I’ve used Photoshop, but I’m pretty sure both GIMP and PS offer two different workflows of saving/exporting your work and they are just named differently and have different keybinds. I have no idea how you can act like you actually tried to use GIMP as something other than a drop-in replacement for PS, but then call the default GIMP project file format “unknown, unused and bizarre”…
No, I’m not talking about project files, they are fine, I’m talking about opening an image, do some basic stuff and saving it. Image editing.
There are two ways to save your work in either program. You can save your actual work, so you can continue editing at some point and not lose stuff like layers, image quality and other information or you can export your work into some kind of image file, optionally compressing it and discarding extra information about the project. I think GIMP even offers a shortcut for this called “Overwrite …”. How is this an issue?
Lol you’re sure tone-deaf.
