News for hackers. Stuff that matters.
Re:Gimp is 25 years old today by jes5199 on Sunday November 22, 2020 @12:00AM (#25175058)
GIMP is such a strange tool. I actually have used it, semi-frequently - since the 90s! The overall experience of using it has only changed a little in that time. And it gets the job done. I guess that makes it successful! What else has been so stable?

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.

Re:Gimp is 25 years old today by megameter on Sunday November 22, 2020 @01:25AM (#25175428)
The way I would put it is: GIMP has features, not workflow.

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.

Re:Gimp is 25 years old today by ehsankia on Sunday November 22, 2020 @04:02AM (#25176046)
Actually, the way I would put it is that GIMP is the perfect example of why companies hire UX designers. GIMP is textbook example of how software can technically have all the same features, but be insanely hard to use and utterly confusing to anyone without a guide. Compare it to Photoshop which does more or less the same things but anyone can naturally pick up and use.
Re:Gimp is 25 years old today by pja on Sunday November 22, 2020 @04:36AM (#25176181)
Can they though? I'll admit it's a long time since I've sat in front of a Photoshop window, but I remember it being just as complex to use.

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.

Re:Gimp is 25 years old today by asddubs on Sunday November 22, 2020 @04:47AM (#25176225)
I still remember that time I tried selecting something and moving the pixels of my selection, rather than the whole layer in GIMP. I ended up having to google it and it was a 3-key combination shortcut. I don't remember how to do it in photoshop, but I'm pretty sure I didn't have to google "how to move a selection" that time I used it.
Re:Gimp is 25 years old today by kristopolous on Sunday November 22, 2020 @07:38AM (#25176964)
Audacity has this in spades. Every annoying thing has a bizarre undiscoverable keystroke to invoke a sensible not-broken alternative.

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?)

Re:Gimp is 25 years old today by throwanem on Sunday November 22, 2020 @09:16AM (#25177607)
What's the Photoshop to Audacity's GIMP?
Re:Gimp is 25 years old today by qwertox on Sunday November 22, 2020 @10:30AM (#25178191)
Sound Forge
Re:Gimp is 25 years old today by pja on Sunday November 22, 2020 @05:12AM (#25176308)
Fair. I think you’re expected to float the selection into a new layer and then move the layer, but this is such a common operation for people to want that it ought to be directly available from the Move tool.
Re:Gimp is 25 years old today by chmod775 on Sunday November 22, 2020 @06:27AM (#25176630)
This is how I've been doing it since forever and and at the very least didn't have to Google it.

I did not know another way existed... which also just illustrates the point.

Re:Gimp is 25 years old today by pessimizer on Sunday November 22, 2020 @11:12AM (#25178588)
It doesn't really, because you don't know how to do it in Photoshop either. I've been recently learning Photoshop for the first time after being a long term GIMP user, and I don't find it intuitive at all. If you didn't need google or books to use Photoshop, somebody should tell the enormous industry of websites and books sold to teach it.
Re:Gimp is 25 years old today by kazinator on Sunday November 22, 2020 @02:13PM (#25180123)
Your comment seems disingenuous, because the predominant user interface paradigm in all sorts of programs (file managers, vector editors, text editors, ...) on all sorts of platforms is that when you select something, you can click and drag that selected thing.

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.

Re:Gimp is 25 years old today by chmod775 on Sunday November 22, 2020 @06:57PM (#25182226)
>Your comment seems disingenuous

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.

Re:Gimp is 25 years old today by pessimizer on Sunday November 22, 2020 @11:08AM (#25178557)
In GIMP you can just cut it and paste it, and ctrl-x ctrl-v works, which are pretty much universal in every application. It creates a temporary layer for the selection, and when your cursor is over the selection you'll get the universal 4-axis pointer that means move, and when your cursor is not over it, it will turn into an anchor (whose meaning you can guess.)
Re:Gimp is 25 years old today by riidom on Sunday November 22, 2020 @09:52AM (#25177859)
Well moving the selection is the 3rd thing you can do, what you meant probably is moving the content of the selection. It's controlled by 3 buttons on top of the tools window, and this plus a few other things are worth spending a bit time to learn the basic concepts.

Which is a good advice for PS as well, btw.

Re:Gimp is 25 years old today by asddubs on Sunday November 22, 2020 @04:02PM (#25181065)
i do remember figuring out how to move my selection without moving what's in it. it felt a little bit like gimp was playing a prank on me
Re:Gimp is 25 years old today by acomjean on Sunday November 22, 2020 @09:41AM (#25177780)
Photoshop has a whole industry around teaching how to use it.

They have photoshop conferences, books and magazines. Not something you expect for a piece of software that’s intuitive.

Re:Gimp is 25 years old today by ehsankia on Sunday November 22, 2020 @07:53PM (#25182525)
So does Microsoft Word. I think you're missing the point. Yes, Photoshop has a lot of more advanced options, but the power of UX is being able to balance basic features and advanced features. Sure someone may not be able to do insane tricks, but doing basic stuff is far more discoverable and intuitive to do.
Re:Gimp is 25 years old today by Naracion on Sunday November 22, 2020 @12:25PM (#25179156)
Also in addition to other sibling comments--note that OT mentioned having been using GIMP for 20 years and still being unable to figure out anything new aside from the tutorials he studied. So being "used to" GIMP is evidently (although currently sample size 1) not enough for it to be "easy to use".

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.

Re:Gimp is 25 years old today by bloopernova on Sunday November 22, 2020 @09:01AM (#25177495)
Back in the late 90s when I used Photoshop as part of my Project Support / Sysadmin 50/50 position, I used books that taught me how to do certain things. I think it's just that Photoshop is that much more popular so has orders of magnitude more people writing books and HOWTOs.
Re:Gimp is 25 years old today by ehsankia on Sunday November 22, 2020 @07:55PM (#25182532)
I disagree, I picked up photoshop at the age of ~13 and did most things mostly naturally. I've tried GIMP 4 or 5 different times at various ages and I've never been able to achieve anything without hours of effort and guides.
Re:Gimp is 25 years old today by sunwukung on Sunday November 22, 2020 @03:51PM (#25180958)
I used PS and many other 3D graphics apps commercially for over 10 years, Gimp is sadly not a patch on it. UX is a thing, and Gimp doesn't have that. As a now software engineer, I can see the thought process behind the application, but it's workflow is treacherous. I switched out to Affinity a few years ago, because PS became too bloated/heavy, and Gimp just doesn't cut it for real work imho. I mention this because it was easier to pick up Affinity after a couple of hours than wrestling with Gimp. Same goes for Blender Vs Max/Maya. I hate to say this, because I would like these tool to be more accessible to all
Re:Gimp is 25 years old today by coldtea on Sunday November 22, 2020 @08:19AM (#25177227)
>Is this just partially a "what you're used to is easy & anything different is hard" thing?

I woulnd't say so. Some programs are plainly more confusingly designed.

Re:Gimp is 25 years old today by ngold on Sunday November 22, 2020 @05:04AM (#25176279)
Been using gimp for 20 years, every couple years I try and fail to do even the most basic stuff in photoshop. Then I give up and go back to gimp.
Re:Gimp is 25 years old today by pessimizer on Sunday November 22, 2020 @11:29AM (#25178696)
Photoshop doesn't have a great UI, it was just very early, good enough, and targeted at professionals. GIMP is better in every way for me so far (I've just recently become a Photoshop user), except that CMYK doesn't work well or seamlessly yet on GIMP, making it unusable in a professional context. Other proprietary photo editors that worked with CMYK from their beginning are passing the GIMP as photoshop competitors.
Re:Gimp is 25 years old today by ghaff on Sunday November 22, 2020 @09:13AM (#25177587)
Honestly, I wouldn't pick Photoshop as a particularly shining example of UX. It's probably better than GIMP. But it's also a product that has accreeted features and ways of doing things over the years and is pretty squarely targeted at people who use it all the time professionally. There are lots of different ways of doing the same or similar things.
Re:Gimp is 25 years old today by howlgarnish on Sunday November 22, 2020 @09:20AM (#25177630)
Having many ways to do a thing is arguably better than GIMP, where there's exactly one way to do a thing and you need to find the right option from the right menu under the right icon to use it.
Re:Gimp is 25 years old today by tambourine_man on Sunday November 22, 2020 @09:16AM (#25177608)
>technically have all the same features

>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.

Re:Gimp is 25 years old today by dalbasal on Sunday November 22, 2020 @06:12AM (#25176564)
>> GIMP is the perfect example of why companies hire UX designers.

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

Re:Gimp is 25 years old today by ampdepolymerase on Sunday November 22, 2020 @08:12AM (#25177187)
Calibre may not be pretty but for a CRUD app it is usable. People who have complaints about Calibre generally have issues with its chrome and dated layout but nobody dislikes it because it is hard to use. A default GTK style UI always looks terrible on Windows and Mac, both of which have much higher requirements for user interface defaults. This is especially so with Amazon and iBooks setting differing expectations for how an eReader should look like. The issue with GIMP is with both its UI and its UX. Trying to get work done in GIMP is difficult and challenging. It is not a mere CRUD app like Calibre.
Re:Gimp is 25 years old today by dalbasal on Sunday November 22, 2020 @09:37AM (#25177748)
People like Calibre. I'm not saying it's bad. I'm just using it as a type example. Gnu-ish software is different in a recognizable way from Google, MSFT, etc. Different enough that both strengths and weaknesses are different.

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."

Re:Gimp is 25 years old today by mattkevan on Sunday November 22, 2020 @01:35PM (#25179742)
While I like and appreciate Calibre, its a fantastically useful piece of software and I use it all the time, its UI veers closer to outsider art than what could be considered best-practice interface design.

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.

Re:Gimp is 25 years old today by kazinator on Sunday November 22, 2020 @01:12PM (#25179540)
> Compare it to Photoshop which does more or less the same things but anyone can naturally pick up and use.

Trolling is not appropriate in HN.

Re:Gimp is 25 years old today by colejohnson66 on Sunday November 22, 2020 @01:30PM (#25179698)
How is that trolling?
Re:Gimp is 25 years old today by kazinator on Sunday November 22, 2020 @03:59PM (#25181044)
Feeding the flame war with obviously false bullshit.

"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.

Re:Gimp is 25 years old today by ehsankia on Sunday November 22, 2020 @08:01PM (#25182566)
While I didn't claim anything close to that, and the evidence I have is only anecdotal between me and a dozen peers, I myself learned to use Photoshop at the age of 13, yet the half a dozen times I had to use GIMP, I spent over an hour every single time trying to do basic things such as moving pixels around and doing basic transformations.

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.

Re:Gimp is 25 years old today by kazinator on Monday November 23, 2020 @01:48PM (#25190133)
In GIMP, selection works in a way that runs counter to the predominant user interface paradigm. A selection isn't an object that the user can pick up for direct manipulation. Rather, it's a delimited region of the image which confines the effects of editing. Thus, you can't just select a rectangle (or whatever) and then drag it to move the pixels. So yes, that will perplex the average user. Scratch that, probably every user. In Gimp, the move tool selects the entire layer which contains the pixels that you're pointing to, and moves that. The selection "cross-cuts" through layers. So that is to say, you can make a selection in one layer (say by picking out a shape), and then switch to another layer where that original selection is still in effect and delimits the edit operations.

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".

Re:Gimp is 25 years old today by tsjq on Sunday November 22, 2020 @02:42AM (#25175751)
>The way I would put it is: GIMP has features, not workflow.

very well said. totally agree with this

Re:Gimp is 25 years old today by rozab on Sunday November 22, 2020 @10:29AM (#25178175)
I really, really wish there was a paint.net clone for Linux. Paint.net is windows freeware, closed source since an early release, which is both feature rich and a pleasure to use. It covers 99% of use cases ordinary people have.

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.

Re:Gimp is 25 years old today by dreen on Sunday November 22, 2020 @10:40AM (#25178287)
Yeah, I switched from GIMP to PaintNET and loved it for my simple needs, but because Pinta wasnt what I hoped it would be nowdays I just use http://www.photopea.com on any system, its basically PaintNET in the browser.
Re:Gimp is 25 years old today by executesorder66 on Sunday November 22, 2020 @03:00PM (#25180533)
Re:Gimp is 25 years old today by agumonkey on Sunday November 22, 2020 @12:36AM (#25175210)
It's funny because GIMP is one of the tools I hate the most. It's really hard to describe how quickly I want to say no to just about everything that it does. I'm quite open[0] but I'd rather write perl script with imagemagik than use gimp.

[0] i can love both emacs and vi and even ed, I've used just about any 2d/3d program ever

Re:Gimp is 25 years old today by BuildTheRobots on Sunday November 22, 2020 @03:01AM (#25175818)
> It's funny because GIMP is one of the tools I hate the most.

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.)

Re:Gimp is 25 years old today by mkl on Sunday November 22, 2020 @04:02AM (#25176044)
I use purely mm for most Inkscape projects (not for laser cutting, but some are for my plotter). Set the units in Document Properties and it just works, IME.
Re:Gimp is 25 years old today by riidom on Sunday November 22, 2020 @10:02AM (#25177937)
Yes. I get when people criticize Inkscape for it's UI (personally I find it annoying to re-arrange the side windows), but feature-wise there is nothing left to be desired (except maybe CMYK not sure about that). But whenever I need something to be printed, it goes into Scribus anyway, and there we have CMYK.
Re:Gimp is 25 years old today by Shish2k on Sunday November 22, 2020 @12:07PM (#25179017)
> there is nothing left to be desired

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 :(

Re:Gimp is 25 years old today by riidom on Sunday November 22, 2020 @12:14PM (#25179062)
Good point, that seems indeed not to be implemented. I get the use case for inner borders, could probably be tricked via clipping. But yes, that's definitely another exception.
Re:Gimp is 25 years old today by jfengel on Monday November 23, 2020 @10:04AM (#25187416)
There is a major hole in its lack of support for animation.
Re:Gimp is 25 years old today by tripzilch on Monday November 23, 2020 @05:01AM (#25185170)
> If you're creating SVGs for laser cutting then the inability to nicely use mm as a unit of measure is infuriating.

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.

Re:Gimp is 25 years old today by nnq on Sunday November 22, 2020 @01:51AM (#25175531)
The same here :) I love to work with other software considered user hostile by others, but Gimp... WTF. It's like they took the most horrible stuff from Photohop s horrible UI and mixed it with more horrible ideas... But PS manages to be horrible and still productively usable and had all the required features, like non destructive editing smart objects etc.

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

Re:Gimp is 25 years old today by agumonkey on Sunday November 22, 2020 @07:00PM (#25182245)
I think GIMP kinda suffers the same fate as intel. I remember a lot of efforts went into creating the underlying core for image processing (GEGL ?) but then nothing happened. It's stuck at the blender 2.7 way of life.

They may try to revamp ergonomics and performance. But that's their choice.

Re:Gimp is 25 years old today by tartoran on Sunday November 22, 2020 @02:35AM (#25175725)
Gimp has script fu / python / scheme. It is quite capable of automating and generating images. Gimp is the kind of software you may hate at first but then start to love it for how extensible friendly it is.
Re:Gimp is 25 years old today by ThePadawan on Sunday November 22, 2020 @03:18AM (#25175883)
I tried to automate a simple workflow (resize, reduce color to grayscale) using GIMP just last week. I would want to run this on ~100 files in a folder.

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.

Re:Gimp is 25 years old today by mkl on Sunday November 22, 2020 @03:58AM (#25176031)
Why do you want to do it in GIMP? I like and use GIMP, but imagemagick sounds like the right tool for the job, and what I'd use there. For almost any batch processing, Python or bash-scripted imagemagick gets the job done. If you need some complex feature of a GIMP plugin, that's another story.
Re:Gimp is 25 years old today by ThePadawan on Sunday November 22, 2020 @04:09AM (#25176075)
I simply found that GIMP produced very good results when dithering to 4bit grayscale (I'm converting images to be displayed on an e-ink display).

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.

Re:Gimp is 25 years old today by LaputanMachine on Sunday November 22, 2020 @05:19AM (#25176342)
I also use a 4 bit e-ink display, and there are sometimes large areas of the same color where you can't see any details. After several hours of tweaking I managed to improve the quality, but it's still not perfect.

Do you have some tips / links that could help me improve the dithering even further?

Re:Gimp is 25 years old today by ThePadawan on Sunday November 22, 2020 @05:48AM (#25176474)
I've not investigated very deeply into it.

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.

Re:Gimp is 25 years old today by Phlogistique on Sunday November 22, 2020 @04:12AM (#25176092)
I did this very long ago. It's possible but the documentation was nearly non-existant, it took me a long time to figure it out.
Re:Gimp is 25 years old today by prokoudine on Sunday November 22, 2020 @03:37AM (#25175951)
BIMP plugin for GIMP
Re:Gimp is 25 years old today by agumonkey on Sunday November 22, 2020 @06:58PM (#25182234)
Sure, it's extensible but I was speaking on all the other fronts.
Re:Gimp is 25 years old today by shawnz on Sunday November 22, 2020 @12:16AM (#25175119)
As a counterpoint I often hear people make this argument but I've never found that to be the case. I find Gimp to have a simple interface in which it's easy to find all the features.

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.

Re:Gimp is 25 years old today by herbst on Sunday November 22, 2020 @03:56AM (#25176023)
I too used and liked Gimp ever since. I was forced to use the adobe stack for a while and never managed liking it, it still feels like a huge blackbox to me.

IMO not everyone is made for (or rather trained to) understand and use overly complex uis.

Re:Gimp is 25 years old today by paulryanrogers on Sunday November 22, 2020 @12:26AM (#25175171)
Cut my teeth on PSP then Photoshop in college. Soon thereafter started with GIMP and indeed the different naming and menu organization was a hurdle. Though it wasn't too bad. Still Photoshop was always ahead in features and most things were more logical.
Re:Gimp is 25 years old today by TylerE on Sunday November 22, 2020 @02:55AM (#25175796)
Gimp, today, feels like a bad knockoff of what Photoshop was in about 2002.

And Photoshop has gotten a _lot_ more powerful and useable since then.

Re:Gimp is 25 years old today by gorgoiler on Sunday November 22, 2020 @12:50AM (#25175251)
Adding a second UI to the codebase (with a friendlier, less conflict inducing name) would be a fantastic addition to the project.

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/ ]

Re:Gimp is 25 years old today by prokoudine on Sunday November 22, 2020 @03:51AM (#25176000)
Glimpse is GIMP minus one brush, one menu item, and GIMP branding, plus Photoshop shortcuts, plus a few popular plugins. That is all it is at the moment.
Re:Gimp is 25 years old today by kazinator on Sunday November 22, 2020 @03:32AM (#25175931)
> Having a single rapid workflow for saving an edited PNG.

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.

Re:Gimp is 25 years old today by gorgoiler on Sunday November 22, 2020 @06:12AM (#25176570)
Thanks. I feel stupid now.

I guess I would have expected this to be called “save”?

Re:Gimp is 25 years old today by noir_lord on Sunday November 22, 2020 @07:03AM (#25176805)
Not same thing, Save implies you want to save the work in progress, so xcf typically (thats the gimp project format, so you can do things like undo stuff etc).

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.

Re:Gimp is 25 years old today by kazinator on Sunday November 22, 2020 @11:38AM (#25178763)
You just have to read the whole File menu (of every program you use, not just GIMP!)

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.

Re:Gimp is 25 years old today by hakfoo on Monday November 23, 2020 @12:33AM (#25183883)
I feel like this was a behaviour shift at some point within the last 25 years. There was a time when you'd open a PNG, and the default "save" just gave you a flattened PNG. Or maybe it did so but complained about the risk. Either way, it felt off to make XCF default ONCE you specified a file type (either by opening a PNG/JPG/etc.) or trying to save as such once. You've decided you want to save only a final output, not something with the intermediary magic.
Re:Gimp is 25 years old today by shawnz on Sunday November 22, 2020 @11:34AM (#25178734)
"Save" and "Export" used to be under the same function many versions ago. I am guessing they changed it to avoid data loss.

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.

Re:Gimp is 25 years old today by jobigoud on Sunday November 22, 2020 @02:04PM (#25180037)
Paint.NET solved this by prompting the user when this particular kind of destructive save happen: This format requires all layers to be merged, are you sure you want to merge all layers? yes/cancel.
Re:Gimp is 25 years old today by kazinator on Sunday November 22, 2020 @03:58PM (#25181033)
But with GIMP's export, you can export a JPEG without merging all your layers. They are merged in the image only. Your default filename (like "myproject.xcf") is not affected; Ctrl-S save continues to save that.

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.

Re:Gimp is 25 years old today by starky on Sunday November 22, 2020 @01:15AM (#25175371)
I learned on software like PaintShop Pro and Photoshop, so I find GIMP to be incredibly frustrating software. I use it at work for editing and cropping photos since I don't have access to Adobe's suite and I'm fairly quick at those few tasks. But I just can't be bothered to learn anything more than that when I find it so frustrating and inefficient to use.
Re:Gimp is 25 years old today by jansan on Sunday November 22, 2020 @04:45AM (#25176218)
I am actually using PaintShop Pro 7.04 until today. It is good enough for 95% of my bitmap graphics work and it just feels so easy to use.
Re:Gimp is 25 years old today by throwawaylolx on Sunday November 22, 2020 @04:44AM (#25176213)
I only ever use GIMP out of necessity and when I do I can't wait to stop using it. I never had a pleasant experience using GIMP and it almost never failed to frustrate me. Just yesterday I had to use it, and this is what my search history looked like: https://i.imgur.com/ZP3U17i.png . I'm pretty fluent in Photoshop and I've also begrudgingly used GIMP for many years. It's a very bizarre tool.
Re:Gimp is 25 years old today by sildur on Sunday November 22, 2020 @04:50AM (#25176234)
Both, Photoshop and GIMP are really complex programs with steep learning curves. I tried to do some editing in Photoshop, since I now have a license, and I was totally lost. I tried to add some guides so I could draw a rectangle to cut a image. I tried dragging from the border of the image, as I do with GIMP, and no way. So I resorted back to GIMP, not wanting to spend half an hour trying to learn how to select and cut an image in Photoshop when I already know how to do it in GIMP.
Re:Gimp is 25 years old today by thraway123412 on Sunday November 22, 2020 @08:07AM (#25177139)
This looks like another instance of "I don't know how to use gimp, but I know how to use photoshop, therefore gimp is a very bizarre tool."

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.

Re:Gimp is 25 years old today by kazinator on Sunday November 22, 2020 @12:19PM (#25179107)
> this is what my search history looked like

> 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.

Re:Gimp is 25 years old today by zokula on Sunday November 22, 2020 @12:59PM (#25179454)
> I never had a pleasant experience using GIMP and it almost never failed to frustrate me.

Funny! I hear the same complaints about Photoshop only the amount of complaints are 10 times as much.

Re:Gimp is 25 years old today by app4soft on Sunday November 22, 2020 @05:59AM (#25176521)
> GIMP is such a strange tool.

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

[1] http://grafx2.chez.com/

[2] http://grafx2.chez.com/index.php?article4/version-history

[3] http://grafx2.chez.com/index.php?article7/1990s

Re:Gimp is 25 years old today by usrusr on Sunday November 22, 2020 @12:18AM (#25175130)
Quite similar situation here: it's the tool that I know but that I will never master. I'm not bothered much by the UI though, it gets the job done well enough for the occasional pixel task. What I mind much more is the atrocious startup time (might be a peculiarity of wingimp)
Re:Gimp is 25 years old today by kazinator on Sunday November 22, 2020 @03:46AM (#25175977)
It's starting in about 3 seconds for me, on a laggardly 2013-vintage Core i5 CPU, 32 GB RAM, Windows 10.

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).

Re:Gimp is 25 years old today by riidom on Sunday November 22, 2020 @10:10AM (#25177987)
Check your version and likely you should update (if you don't rely on plugins that aren't ported yet). Startup time was increased by a huge amount some time ago (can't remember when exactly).
Re:Gimp is 25 years old today by prokoudine on Sunday November 22, 2020 @04:32PM (#25181298)
Summer 2018 when async fonts loading was introduced.
Re:Gimp is 25 years old today by taharvey on Sunday November 22, 2020 @01:59PM (#25179981)
Interesting milestone, worth reflecting on the broader failures of OSS.

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.

Re:Gimp is 25 years old today by Lipsey on Sunday November 22, 2020 @12:10AM (#25175096)
I found it odd coming from tools like Macromedia Fireworks or Coreldraw because I was expecting to add shapes, fill and pan objects in the canvas. But as soon as I grasped the difference between vector based and raster based tools and why layers are important it became easy.
Re:Gimp is 25 years old today by swebs on Sunday November 22, 2020 @06:37AM (#25176676)
>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.

I feel the same about Latex

Re:Gimp is 25 years old today by pjmlp on Sunday November 22, 2020 @08:28AM (#25177272)
I share the sentiment, for a while I was also big into Gimp, even bought books as means to support some of the developers, eventually as I went back to Windows as my main driver, I ended up settling in Paint.NET.

It does everything I need in a couple of mouse clicks without going through tutorials every time I need to handle some images.

Re:Gimp is 25 years old today by edgyquant on Sunday November 22, 2020 @12:11AM (#25175097)
Yeah you just described me too. I learned it as GIMPShopPro (a resin for Windows that looked liked photoshop) and when I switched to Linux in 2007ish I learned the basics of normal GIMP and have used it weekly ever since without learning anything new. Never thought about it until now.
Re:Gimp is 25 years old today by vmception on Sunday November 22, 2020 @12:53AM (#25175266)
That started off surprisingly generous.

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.

Re:Gimp is 25 years old today by moonbug on Sunday November 22, 2020 @04:53AM (#25176244)
You'll be wanting Glimpse https://glimpse-editor.github.io/
Re:Gimp is 25 years old today by darig on Sunday November 22, 2020 @12:13AM (#25175107)
I've also been using GIMP since the 90s... but I'd say the overall experience has changed drastically and done so many times. I use a lot of Plug-ins, and somewhere in the mid 2000s the communication between them stabilized and sped up dramatically to the point that I all but ditched photoshop. Then I switched to an all mac shop, but GIMP's X11 interface on a mac was terrible, so I was back on photoshop. Then, fairly recently, GIMP switched to all native windows on mac, with tons of new windowing and tiling options that feels as responsive as photoshop, so I'm back to 100% GIMP.

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.