Hacker News new | comments | show | ask | jobs | submit login

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.

Yeah, well I want flying cars, but the physics just doesn't make it practical. Neither is what you're talking about. Just take the extra steps and be glad you're not paying for Photoshop.

It's perfectly practical. GIMP did exactly that for years. The 2.8 release notes[1] 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[2]:

> 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[3], but then I realized that's only a patch in the unofficial OS X build. On Linux, the same nonsense in the latest version.

1. http://www.gimp.org/release-notes/gimp-2.8.html

2. http://registry.gimp.org/node/26273

3. http://gimp.lisanet.de/Website/News/Eintrage/2013/3/21_GIMP_...

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

Yes, this behavior would be equivalent to "flying cars". Yeesh, how ridiculous. I'd happily pay for photoshop. It's a better program and easier to use.

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.

Regular users still don't understand why GIMP complains, only know it's hard to do what they need to do anyway.

GIMP should have option "also save as native format in image repository" that is on by default, if the developers care so much about the conversion losses.

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | DMCA | Apply to YC | Contact