this post was submitted on 11 Nov 2024
983 points (98.4% liked)
Programming Humor
2644 readers
144 users here now
Related Communities [email protected] [email protected] [email protected] [email protected]
Other Programming Communities [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected]
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
And their invented forced onto you file system 🤢you can't open a jpg, change sonething and then you jhave to dance around the export, nit save when clising etc etc. Why devs, why?
Would be super cool if they got things up just a bit.
When you're opening a jpeg it is transformed into a Gimp datafile so you can edit it.
"Saving" as jpeg would remove all your editing history, collapse all layers, and perform lossy compression on the resulting image.
Since losing most of the info included in your open file is not really what you want when you hit "save", they put it behind the "Export" button.
I guess it would be more logically consistent if the workflow for editing images was to create a new Gimp project, then import a jpeg into it, the way some video editing software does it.
But that would be even less convenient.
Yeah I know, I just don't want to save that clutter in a file format you can't use elsewhere.
Photoshop only makes you save in the .psd format if you have added layers, data outside the image etc. Otherwise it just saves it to a jpg or png or whatever it was when you opened it. This is the correct way IMO.
you can't do what ? I have trouble following you
They are complaining that Gimp only allows to save in reconstructable formats (e.g. xcf) even when you opened baked fileformats (in this case jpeg)
In Gimp you have to export to those file formats as you would lose layer and history data as they don't support that.
ah, yes, saving and exporting used to be conflated. That shouldn't be a problem, just hit export instead of save
Yeah and then when you close the image it says it hasn't been saved, which is both annoying and error prone.
Not a super big deal you'd say but when you resize lots of images it is, for example. Especially as it worked differently and one day they forced this bad UX choice.
I see how that’s useful for workflows…
I have the same complaint with Affinity Photo when I make Star Trek memes and now have a bunch of .afphoto project files, when I’m often just adding text to a jpeg.