Getting OT here, but the thing that kills me about Gimp is how badly it doesn't want to save the file in its original format. You have to export it (totally different menu option) and then it will whine when you close the file because it thinks you haven't saved it.
The thing almost every user expects it that saving the file just saves over the old file in the format it was originally in. IIRC, it used to work that way, and then one day it changed for the worse.
That's a recent change, and yeah, one of the worst examples lately of open source developers' contempt for their users. Apparently, those of us who've used Gimp for over a decade to edit .jpg and .png files and save them back to .jpg or .png, were Doing It Wrong, and the devs wanted us to know. :(
Mind you, I've never contributed the tiniest bit of code or funding to Gimp, so I can't really complain.
> one of the worst examples lately of open source developers' contempt for their users.
That's utterly silly. If you take yourself seriously as a graphics editing program, then inevitably you have to move to one format that you can then convert into others. Otherwise you have to implement every single operation on every single file format you support. With the One True Format, (.otf) you can convert your .jpgs to the .otf and then do the operation there.
This then presents a problem. Tech-savvy users know that there will be a loss of data when you save to a consumption format. But the rest of us don't. If you allowed open and save in the same format, people will make the intuitive leap, that they're actually editing the files in that format, when they're not. They'll think all the layers they made will carry over into the PNG and that they'll be there when they re-open the file, when in fact they won't.
It would be a nightmare, because nobody will know what will save and what won't. You'd have to then educate users that to get everything to save properly, you have to save to .otf. Or you could just bake that logic directly into the app.
I think the way to do that--and the way I've seen it done in other contexts--is to detect what features can't be saved in the original format and warn the user about about it (with an "I don't care about this" checkbox). I think Word does that when you make a bunch of changes to a document in an older format and are saving it back.
I know users don't read, etc, but the trade you're making is that the simple process of editing a file and saving it is now much more annoying. I just want to make changes to my PNG, not deal with the One True anything.
It's perfectly practical. GIMP did exactly that for years. The 2.8 release notes mention removing the warning now that save and export are separate.
The stated goal was to make it harder (still? I guess people clicked through the warning without reading) to accidentally save in .png or .jpg and lose the layers. But the result, for someone whose usual workflow is to open a .png/.jpg, edit, and save back to .png/.jpg, could not be more user-hostile and obnoxious.
In response to a complaint, someone on the forums wrote:
> This is the way Gimp now works. Of course you can consider this a PITA. But for other folks, losing work because they saved as JPG instead of XCF is also a PITA. The philosophy is that people that are impacted negatively by this change are people with very simple work-flows who would be better off using simpler software (XnView, Digikam, Lighttable...)
In other words, all of you people with simple workflows, that worked just fine in Gimp for years? Now you have to go off and learn some new software, because Gimp is for Serious Graphic Design™ only. Ugh.
I got excited researching this because I found a changelog for Gimp 2.8.4 that mentions patching the behavior to be sane, but then I realized that's only a patch in the unofficial OS X build. On Linux, the same nonsense in the latest version.
The existence of several counterexamples of it done would seem to disagree with your point about it being "impractical". Paint.NET warns it'll have to flatten layers when saving as PNG, Notepad will warn if you try to save Unicode-laden text to an ANSI .txt... not to mention several blanket warning systems...
It's not "utterly silly". At least hear and respect the opposing view rather than dismissing it. Least surprise is one of the core principles of usability.
Every program I use saves to the original format by default, most warning you if there will be data loss. Whether you like it or not, this is how software works and how users expect it to work. If you want to automatically backup a different format that's fine.
If you want to save the full format of the file, including layers and whatever other GIMP magic you've created, you'd best save it in GIMP-native format.
If you're just doing some quick tweaks, you'll get used to the export option and ignore the prompt to save on quit.
Since most of what I do are quick edits of screenshots, the latter works fine for me. If I were a graphic artist, I'd probably get more than slightly peeved if my afternoon's work were lost due to an incompatible file format save w/o prompt.
Not prompting the user leads to massive loss of user work and state. Prompting the user is a minimal overhead to avoid this risk.
Considering it's a relatively recent change, it certainly has come as a suprise to lot of users. Did to me. Did to my wife. Bit at least a couple of friends I know.
From a technical point of view I can certainly approve the change. Back in my time I've had couple of my images ruined by badly timed save (user error [tm]), so the non-destructive approach certainly has its merits. However, the new behaviour breaks a lot of ingrained casual use flows. So maybe the best approach would for Gimp to remember the original filename when it's opened and if the filetype is anything except XCF, simply do two saves: create a new $filename.xcf automatically with all the changes the user has made, and also auto-export with the old name.
That way the more casual users could still just do "open, edit, save" for their quick edits. As a bonus, since the XCF file is non-destructive, the original file would still be in there. This might give the best of both worlds: it wouldn't break existing workflows, and it would automatically prevent accidentally changing the original image. Plus it would make the save/export split less of a headache for new users.
Photoshop does that as well, Illustrator is especially bad for it. There are specific reasons for it, that you don't want to save a file and realise you've lost all your layers because it was saved as a jpg.
If you're a casual user, sure. If you're serious, the lack of adjustment layers alone will cause you to rip your hair out. Gimp is fine for Joe Bloggs making a banner for their site; but honestly it's pretty mediocre, with a horrid interface and missing functionality.
(To be fair, some of that last bit is due to Adobe patents)
Well, that actually a very important point. Clearly adoption of free software is much lower than one could expect. What I mean is: you can argue that Gimp is not as good as PhotoShop, LibreOffice not as good as Office, or that Linux is not as good as Windows (which is clearly debatable) but they are good enough and they are all infinitely cheaper (literally) than their paying alternative. So that should be default choice for 99% of people. But it isn't.
So my point is: The same goes for cars vs. bikes. Most people wouldn't mind using a bike to go to work, but it feels weird to pay only a couple of bucks for a bike, when you've learn that the price to go to work is the price for a car.
I was more referring to compatibility, here. LibreOffice is infamous (at least around here) for mangling table formatting used in Word docs. Gimp is hardly feature complete compared to photoshop.
The reasons for this could probably be rightly chalked up to obfuscation and other below-board shenanigans on the part of certain companies, but the end result is still that you don't use the FOSS version if you're serious.