I’m starting this off by saying that I’m looking for any type of reasonably advanced photo manipulation tool, that runs natively under Linux. It doesn’t have to be FOSS.
I switched to Linux, from Windows, about three years ago. I don’t regret the decision whatsoever. However, one thing that has not gotten me away from Windows entirely, is the severe lack of photo editing tools.
So what’s available? Well, you have GIMP. And then there’s Krita, but that’s more of a drawing software. And then…
Well that’s it. As far as I know.
1. GIMP
Now, as someone migrating from Photoshop, GIMP was incredibly frustrating, and I didn’t understand anything even after a few weeks of trying to get into it. Development seemed really slow, too. It’s far from intuitive, and things that really should take a few steps, seemingly takes twenty (like wrapping text on a path? Should that really be that difficult?).
I would assume if you’re starting off with GIMP, having never touched Photoshop, then it’d be no issue. But as a user migrating, I really can’t find myself spending months upon months to learn this program. It’s not viable for me.
No hate against GIMP, I’m sure it works wonders for those who have managed to learn it. But I can’t see myself using it, and I don’t find myself comfortable within it, as someone migrating from Photoshop.
2. Krita
Krita, on the other hand, I like much more. But, it’s more of a drawing program. Its development is more focused on drawing, and It’s missing some features that I want - namely selection tools. Filters are good, but I find G’MIC really slow. It also really chugs when working with large files.
Both of these programs are FOSS. I like that. I like FOSS software. But, apart from that, are there really no good alternatives to Photoshop? Again, doesn’t need to be FOSS. I understand more complex programs take more development power, and I have no problem using something even paid and proprietary, as long as it runs on Linux natively.
I’ve tried running Photoshop under WINE, and it works - barely. For quick edits, it might work fine. But not for the work I do.
So I raise the question again. Are there no good alternatives to Photoshop? And then I raise a follow-up question, that you may or may not want to answer: If not, why?
Thanks in advance!
GIMP has its share of issues, just like any other software. but it’s biggest issue is that somewhere down the line general users got this idea in their head that it was supposed to be a Photoshop clone.
So they go into it with certain expectations and then get frustrated when it doesn’t work that way. People like me, who actually learned GIMP before PS, obviously didn’t go in with the same bias and therefore have a much better grasp on it.
Gimp is not a Photoshop clone. it’s its own piece of kit with it’s own design and feature decisions that some may like and others may not. That’s life. The developers have no obligation to follow any other software design scheme any more than Sony is obligated to follow LGs TV UI. They’re not clones, they’re alternatives.
if you think Gimps only function is to copy Photoshop, you’re in for a bad time. If you want to use gimp as an ALTERNATIVE and go in without the bias, you’ll likely learn your way around a LOT faster.
I’m not excusing Gimps failings. far from it. but I AM saying that half the issue is the Photoshop users thinking that gimp only exists to copy everything from their precious Adobe daddy. And that’s simply not true.
Honestly I feel like this attitude is the reason GIMP’s UX suffers. They’re so determined to be “not like photoshop” that they’re unwilling to fix some of their more boneheaded UI decisions out of fear that they’d be seen as copying photoshop.
That’s not exactly my impression from following the design conversations through the years. They’re more approaching decisions from the angle of what they think is best, their philosophy is to plainly ignore what others do and follow their own direction. Of course taking inspiration from Photoshop might sometimes be a good thing, if it doesn’t conflict with the GIMP way of doing things.
I’ve noticed in recent years some newcomer devs have had discussions on how to design their contributions, mentioning Photoshop and other alternative ways and there were just conversations about the merits of the different approaches that could be taken and what would fit the GIMP best, without bias.
Anyway, I wasn’t aware that GIMP UX suffers, I’ve never used anything else and am happy with it. It seem logical to me, obviously with fewer features than Photoshop but how much can a couple of guys do and they’ve had to refactor most of the GIMP for 3.0, but that’ll open up for a lot of functionality being added moving forward…
Anyway, I wasn’t aware that GIMP UX suffers, I’ve never used anything else and am happy with it.
My argument here is that by never having used anything else, you wouldn’t necessarily realize how much better other UX choices could have been.
That said, I do have to give the devs some credit, as they have fixed two major issues, by adding single-window-mode and unifying the transform tools. Having each transform be its own separate tool was just awful UX IMO.
The biggest remaining UX problem, in my opinion, is the way GIMP forces layers to have fixed boundaries. Literally no other layer-based image editor has fixed layer boundaries, because it makes very little sense as a concept. Layers should solely be defined by their content, not by arbitrary layer properties set in a dialog box.
If you want to use gimp as an ALTERNATIVE and go in without the bias, you’ll likely learn your way around a LOT faster.
I think this is the key phrase – do you want an alternative (where you might have to learn new ways of doing things), or do you want a clone? GIMP is not a clone, but an alternative.
I also think this gets to something I was told loooooooooong ago, when I was a young lad asking what was the best computer to buy. Someone told me, “Find all the software you want/need to run, and get the computer that will run it all.”
In other words, if you need to use Photoshop, then maybe you don’t use Linux – maybe stick with Mac or (shudder) Windows.
I always love it when Linux users recommend going back to Windows as a option. It takes real maturity to admit that everything is a viable option, and sometimes especially in a professional workplace that Windows and MacOS should both be considered if Linux is limiting your workflow.
@displaced_city_mouse @Adderbox76 yeah I’m fairly OS agnostic, I hate them all…just hate Windows more which I think you might agree with considering the shuddering induced by mentioning Windows 😏 I use ChromeOS, Mac, & iOS daily bc for my uses they are least problematic. Use Win 10 for gaming but looking to switch to Linux not W11 for that and have been dabbling/learning Android & Linux. Honestly it’s a good time to be a nerd IMHO.
Agree, partly.
I’ve migrated to a lot of different programs since switching to Linux: Premiere to Resolve, 3DS Max to Blender, to name a few. And I never expected the switch from Photoshop, which I so dearly love, to whatever good alternative that exists - to be easy. I’m willing to put in the time to learn GIMP, if only it hadn’t such glaring and prominent issues that make it really difficult to use.
I’m not expecting a clone. I’m not expecting the UI to be the same. And, I’m willing to learn this program from the ground up. But I want a consistent experience - an app that works. For me, GIMP gets in the way a lot; making things unnecessarily difficult just for the sake of being “different”.
I don’t mean to hate on GIMP. It works very well for people who like it. But we all have different preferences when it comes to software, and in the end - It’s just, not a good alternative for what I prefer. I’m willing to learn something new, but from my experience, GIMP will have (and has) a lot of icks that I just need to “put up with” to be usable. Especially efficiency. GIMP does not feel efficient, like at all. Might be because I haven’t learned it, but even Resolve felt efficient the first time I used it.
I don’t have the same experience with Krita whatsoever. And sure, maybe Krita is a little closer to Photoshop than GIMP is, but I much prefer Krita’s overall experience much more than GIMP - even if it’s missing some more advanced features.
I will stick to Krita, most likely, as that’s what I find myself most comfortable with. But it’s been interesting to hear what everyone else’s experiences are.
I had the same experience moving from GIMP to Photoshop. 😂
If I want to erase the white around an object
Funny, this is literally one of the primary examples of something that GIMP did better than Photoshop (at least back when I was actively using GIMP a lot). GIMP has the “color-to-alpha” tool that allows for backgrounds to be faded into transparency (including converting the border of that object into translucent pixels that don’t have the hint of the old background), which I remember being the easiest way to remove sky or other background from an object, and to place that object into a new background or other image.
I’m guessing that in the 10 years since, Photoshop has a bunch of those AI tools that can do that specific function almost automatically. But GIMP does do that specific task pretty well.
GIMP has the closest thing to feature parity. If you’re looking for similarity of UI and workflow, you’re not going to get it. Adobe throws millions of dollars that open-source projects don’t have at streamlining their UI. UI specialists that will work for free are unicorns, so most open-source UIs are designed by volunteer generalist programmers. Which means that said UI gets the job done, but isn’t optimized for the workflow of people who don’t think like the original programmers.
Personally, I might shift the same picture through Darktable, GIMP, Inkscape, and even Scribus, depending on what I was trying to do with it. (Text on a path -> probably Inkscape, then export as PNG and import into GIMP as a layer.) Is that less convenient than performing all the operations in one program? Possibly, but since I don’t like Photoshop’s UI either, I’m willing to give up on “one-stop shopping”.
(So who, for my money, had the best UI? Probably Paint Shop Pro, twenty or so years ago when it still belonged to JASC. Of course, it was a simpler program too, and so had less junk in its interface.)
Fact is, if you’re a pro, you’ve invested years into learning Photoshop’s interface and how to get the best results out of it. You’re in the position of a baseball player who’s decided to start all over again with basketball. Any attempt to transition to other software is going to be really, really frustrating for you, and likely drop your productivity into the toilet for a few months at least. Plus, you’re going to need some features that average users don’t care about, especially if you’re preparing work for print.
I hate to say it, but you may honestly be best off running Photoshop in a VM rather than trying to move to other software, at least until you can set aside a couple of months where you have no urgent projects (if that ever happens).
There’s a script for installing Photoshop with wine on Linux: https://github.com/Gictorbit/photoshopCClinux
it worked for me
Personally, I might shift the same picture through Darktable, GIMP, Inkscape, and even Scribus, depending on what I was trying to do with it. (Text on a path -> probably Inkscape, then export as PNG and import into GIMP as a layer.)
Gotta love this adaptation of the “do one thing and do it well” principle.
I hope we see more composable desktop apps in the FOSS space so that we can at least get more UI options for a given backend. Maybe then we can get closer to what users want. The other option more low code options, so users with more domain expertise and build UXs like they want.
I think one of the most insidious things about Photoshop is that it is a powerful, complex program. Using it is a skill. Which means that even if you think you are getting the better of Adobe by pirating their software, you are still building your own skills with their program, which is so full of features that classes can be taught about using it. In the end, that’s a win for Adobe and their proprietary software, because if you end up getting good enough to make money from that program, you will end up finding yourself in a position where you eventually pay them, or work for someone who does. This is to the detriment of any other photo editor, of course. You won’t care about how good GIMP or anything else is, much less fund it, because you won’t want to use it, because you know Photoshop.
If I had deep wallets I would love to start funding GIMP for development and rebranding. But I don’t have that kind of cash to push around :P
I’ve read that part of why GIMP is the way it is is because it’s meant to be a testbed for the GTK UI library, so features are added to use new UI elements as much as they are to aid photo manipulation, and in some cases it’s considered preferable to use a weird widget so it’s got a test case rather than whichever widget leads to the best UX. I don’t think I’ve ever looked for a more definitive source than a Lemmy/Reddit comment, but it’s at least consistent with my experience of using GIMP.
+1 for Photopea. I found it extremely friendly coming from Photoshop, has a lot of functionalities and works great on computers where I can’t/won’t install Photoshop. YMMV though, since you want to use it as a full replacement and I used it only for simple retouching/modifications when I’m not on the desktop
Another +1 for Photopea from me. I had been on-and-off wrestling with Wine to get Photoshop to run since I had switched to Linux, but since discovering Photopea I haven’t felt the need to bother with that. In addition to the website version, if you aren’t religiously anti-Electron, there’s a desktop app for it on Flathub.
