There are a lot of things that are possible, but not by combining the basic tools and metaphors in sensible ways: each time is more like diving into the command line options of a GNU tool, finding the exact thing, and if you really, really need to automate it, it goes in a script where it can be safely forgotten.
Which is, certainly, a way of doing, but not one conducive to pleasurable use or professional scenarios where you need to have it pass through multiple hands.
Is this just partially a "what you're used to is easy & anything different is hard" thing?
What exactly makes Photoshop easier to use in your opinion? This is a genuine question - I see this asserted so often, like it's a truism, but nobody ever seems to give specific examples.
Why they don't make the reasonable implementations the first class defaults is way beyond me... (I haven't read the mailing list/bug report threads enough to find out, if someone has insight I'd love to know. It's like they know something is what people don't want to do 99.9% of the time, they fix it, then they hide the fix; ie deleting some audio without shifting everything over - I have never wanted to shift things on delete. Not once, never. Not a single time. Why is that default?)
I did not know another way existed... which also just illustrates the point.
This is a thing that is different in GIMP: that the selection specifies an area of the image which is affected by operations, rather than an object to manipulate.
"I did not know another way existed" seems outlandish. I mean, launch any paint program developed for any platform in the last 40 years; chances are you can select a rectangle and just drag it.
There is a rhyme and reason to the way GIMP does it, and you can learn it quickly, but it's going to cause complaints.
It could be that 99% of the anti-GIMP ranting is caused by this one issue.
Your comment seems like you missed what was being talked about. In fact you appear to think I was arguing a point antipodal to what I was actually saying.
"I did not know another way existed" was referring to a second way to do it in GIMP.
Which is a good advice for PS as well, btw.
They have photoshop conferences, books and magazines. Not something you expect for a piece of software that’s intuitive.
Edit. I'm not saying Photoshop is easier to use--it might be just as difficult but with better resources available people might be able to learn it better.
I woulnd't say so. Some programs are plainly more confusingly designed.
>does more or less the same things
Photoshop has way more features than GIMP. GIMP has some severe basic wholes like lacking CMYK support after 25 years. I think they rather wait for printers to be obsolete than actually spend time implementing the color mode.
Whole I agree that this is UX design, but I suspect that UX can be (and often is) a product of the type of organisation producing it moreso than the "UX designer hired to do UX." UX for something like Gimp is very hard. The metaphors have to encompass a ton of stuff and the UX needs
A web app created by a bank, electric company or somesuch will tend to be different from an app created by an SV-ish company in a pretty predictable way. Similarly, Gimp seems like a relative of other GNU/OSS software... Calibre comes to mind.
Different types of organisations or ways of doing things have different strengths and weaknesses. Th
With Calibre, most users won't feel like they have a grasp of what the software is and what you can do with it... compared to an Apple product. But, it's super powerful and the answer to a lot of "how do I X?" queries is use calibre. Without calibre, the operative answer would probably be "you can't."
GIMP, however, is more like when an ecosystem is cut off for millions of years and there’s no natural predators so things evolve in strange and highly localised ways.
GIMP is the duck-billed platypus of software.
Trolling is not appropriate in HN.
"People are born with the ability to use the program that I offer in contrast to the impossible-to-use crap being discussed. Literally anyone. Even babies who couldn't latch on to a boob for the first two months of their life can use it, whereas that other monstrosity requires a Ph. D. in computer graphics or signal processing."
Come on; it's not 1995, and this is not comp.sys.os.advocacy.
Look around the thread and you will hear dozens of similar stories.
I'm sorry but I didn't know telling my own experience counted as trolling.
The way you move pixels in GIMP, though it doesn't conform to certain well-established user interface conventions, is learnable (and even discoverable). By the time you used it half a dozen times, you should have picked it up on it.
The way you're evaluating these programs is the equivalent of comparing cars by kicking their tires, slamming the door, and honking the horn.
> I didn't know telling my own experience counted as trolling.
Exact words: "Compare it to Photoshop which does more or less the same things but anyone can naturally pick up and use."
That doesn't at all look like telling one's own experience.
Also, your experience consists of evaluating use cases from Microsoft Paint on advanced image editing tools, then it's not relevant enough.
Your comment amounts to what HN calls "shallow dismissal".
very well said. totally agree with this
I believe the author closed the source after some other projects tried to use it commercially. It still gets regular updates.
There's an attempt at a clone, Pinta, which was based off the early open source version but it didn't get much further than mspaint functionality.
[0] i can love both emacs and vi and even ed, I've used just about any 2d/3d program ever
You've obviously not tried to replace Adobe Illustrator with Inkscape ;)
(edit: a flippant comment backed by much frustration. If you're creating SVGs for laser cutting then the inability to nicely use mm as a unit of measure is infuriating.)
Pretty much every time I’m working with vectors, my shapes have borders, and I want to control whether the borders are inside, on top of, or outside the shape (similar to eg box-sizing in CSS terms). As far as I can tell, inkscape still doesn’t support that :(
I do this all the time (for my mechanical plotter).
InkScape is an incredibly useful tool that can do some things that Illustrator chokes on (doesn't always load standards compliant SVG correctly and/or does weird proprietary shit) -- and vice versa, but I think there could actually be reason to install and use both.
Something like Affinity Photo is the other end of the spectrum, with nice and intuitive UI for almost everything... Though it stills falls short of old Corel Photopaint's nice and intuitive UIs
They may try to revamp ergonomics and performance. But that's their choice.
This takes a few lines of calls to imagemagick/gm or ~10 lines of python + Pillow.
Do you have any resources how to do this in GIMP?
After googling for a good while, I could not for the life of me figure out how to even get started with this.
I don't want to write an extension for GIMP - I want to use GIMP like I would an image manipulation library.
I'm sure I could get any other lib to produce the same results, but only after an hour of tweaking. That is what I ended up doing after all, because learning how to automate GIMP was harder.
Do you have some tips / links that could help me improve the dithering even further?
For my use case (a digital picture frame), I've simply rejected images that looked very bad after dithering, and that's very often
- (a) generally dark images,
- (b) very gradient-based images (banding appears) and
- (c) art with a color spectrum that's very narrow in lightness, but wide in value (i.e. most colors map to the same level of gray after converting to grayscale)
Besides using Floyd-Steinberg dithering, I have not tried anything fancy.
As I mentioned above, the exact quality of differing varies by a large amount depending on the tool. I would recommend comparing the quality of GIMP vs. other tools on a single example image.
However I never used Photoshop or Paint Shop Pro. I have found that people who cut their teeth on Photoshop seem to consistently find the Gimp UI confusing.
IMO not everyone is made for (or rather trained to) understand and use overly complex uis.
And Photoshop has gotten a _lot_ more powerful and useable since then.
Something along the lines of a cooperative fork, I suppose, focused on exposing a minimal set of features but keeping the underlying image processing models.
Fewer buttons. Distilled UI. Having a single rapid workflow for saving an edited PNG.
[...and this is almost exactly what Glimpse is, thank you other commenters!: https://glimpse-editor.github.io/ ]
You mean instead of two rapid workflows?
1. File -> Overwrite Existing <whatever>.png.
First time it is used, there is prompting. After that, no prompting. Has no hotkey.
2. Or use Export As, which has a Shift-Ctrl-E hotkey.
The first time you use Export As, there is prompting. But after the first use, the "Overwrite Existing <whatever>.png" menu item (for workflow 1) disappears from the File menu and is replaced by "Export To <whatever>.png". This action has no prompting at all, and has Ctrl-E as the hot key.
Workflow 1 has less initial prompting than 2; it goes straight to the Export dialog (for setting parameters) without prompting for a filename or overwrite confirmation; it's good if you're editing many images and saving just once.
I guess I would have expected this to be called “save”?
Export is well export "Take this project and make it <Foo> format with <Bar> quality" settings.
It's the way many print/graphics packages split it conceptually.
In GIMP, saving refers to persisting the project in the native .xcf format. Everything else is exporting.
Exporting loses information, that's why it's not called saving. It can use lossy compression, first of all. And then, the target format might not support all the semantics. For instance, it might not support layers, or not support layers with all their GIMP nuances, like layer masks and whatnot.
If you're working on a PNG or JPEG and want to close GIMP and continue later without any loss of data or disruption, you have to save the project as an .XCF.
Consider if someone "saved" into a format that does not actually support all the features of Gimp, like PNG. They might be surprised when they open their file and things like layers are missing.
GIMP's export is smart enough not to keep prompting you. You are prompted once to set the parameters, like compression and others. Then you can repeat the export operation with no prompting. You have a Ctrl-E hotkey to do that instantly, and Ctrl-S continues to save your project to the .xcf file.
I'm pretty fluent in Gimp, and I only ever use Photoshop out of necessity, and I'm always totally lost when I need to do that.
> gimp resize image
Image -> Scale Image
Very bizarre, indeed! Scaling the image is a "Scale Image" command in an "Image" menu.
> gimp rotate layer
Layer -> Transform -> Rotate { 90° Clockwise, 90° Counter-Clockwise, Arbitrary Rotation ...}
Totally undiscoverable. Rotating a layer is buried in the completely unrelated Layer menu and obfuscated by terminology. The user has to be a propeller-head who knows bizarre jargon, such as that a rotation is a kind of "transform" and might be hiding under a menu item labeled that way.
To add insult to injury, this menu item has not moved in at least 15 years to a more obvious place. Gimp clearly likes existing users better than new ones.
> gimp rescale interactive
In the latest stable Gimp (2.10.22) which I just installed last night, there is a surprise: I can't find the Rotate tool button. Aha, there is an "all in one" transformation tool. The Gimp version I previously used still had separate toolbar buttons for different transforms.
I see that we can right click on the all-in-one transformation button, and then pick a specific kind of transform. We want Scale, which is also available as the familiar Shift-S hotkey.
The Tool Options dialog comes up for the tool. I see that the very first item is a bunch of icon-labeled buttons next to a Transform: label. They all have tooltips: "layer", "selection", "path" and "image". Aha: Transform -> "image" must be what we want. We click on that.
Now we proceed to interactively rotate the image, and apply that change using the Scale button on the rotate dialog.
In summary: Shift-S to scale, pick "image", do the interactive scale, and click "Scale" to make it stick.
For your other queries, you just have to know how to work with transparent layers in Gimp. Gimp is not a carbon copy of Photoshop.
You were not born knowing how to erase pixels transparently in Photoshop.
Funny! I hear the same complaints about Photoshop only the amount of complaints are 10 times as much.
GIMP is less strange than AzPainter[0], even less strange than GrafX2[1].
FTR, Grafx2 (GrafX 2.0 and beyond) would celebrate its own 25th Anniversary next year.[2]
But really, development of the first version of GrafX2 (GrafX 1.0) started in 1995.[3]
> GRAFX 2.00 Beta 90% (11/01/1996) - Wired'96 release
> This version was 1st shown at the Wired'96 demo party in Belgium. We gave it to many people there, so let's start history from here. Note that there were a few different "90%" versions because we didn't want to change the number just for tiny bug-fixes.
> GRAFX 1.0? -> 1.02 (09/??/1995 -> 07/??/1996)
> Forget it!
So, Grafx2 & GIMP are age-mates, but GrafX2 maybe is 'older brother'.
[0] https://github.com/Symbian9/azpainter
[2] http://grafx2.chez.com/index.php?article4/version-history
I know what you're talking about; historically there used to be a long pause in the startup progress bar of the Windows verison, stuck on scanning system fonts or something. But I don't see that in the current version (2.10.22).
Open source user-facing software like Gimp, Openoffice & inkscape were supposed to be the wave of the future that would eclipse their commercial counterparts over the next decade.
But OSS developers turned out to be daft to UI/UX concerns and lacked user-centric empathy to make software that would ever really matter in the marketplace.
Meanwhile the OSS marketplace that did takeoff in stunning ways were developer frameworks, libraries and building blocks (ie. everything on Github). Which developers then used to build the far more insidious world of SaaS. Where couldn't even own the software at any price, and more dastardly... you can't own your data.
I feel the same about Latex
It does everything I need in a couple of mouse clicks without going through tutorials every time I need to handle some images.
GIMP is 25 years old and still sucks. And as we have all learned over that same time span, free stuff has competition and quality controls too.
I'm leaving out a ton of bug fixes and optimizations and new features over the years that were game changing to my processes. It's never stopped getting better. The only software I'd say has improved so much so consistently is OBS.
But of all the software I have ever used, GIMP is the most difficult to learn. I memorized a few tutorials, this must have been around Y2K, to do the a couple things. And basically I have never figured out how to do anything else in it. After twenty years. Sometime, more than a decade ago, they made the tool icons both harder to recognize visually more unpredictable in their toolbox layout, and that still slows me down, too.
I just can't think of anything else I've had this kind of relationship with - other tools, I either master, or I move on from. GIMP is an odd one.