Gimp 2.10.32 Released | Hacker News Reader

Gimp 2.10.32 Released

gimp.org

42 pointsmarcodiego8 comments

Nice to see they're also updating bugs and not just messing with the UI.. The last time I updated it messed with the toolbox, I can't remember what it was, like, some tools missing and you had to long-press to get to them or some nonsense like that, and probably made the icons more abstract too, to the point where I couldn't find out what stuff was anymore.. Had to dig through options to get it back to the old way..

I'm generally finding this to be a problem with all software these days, the constant itch that must be scratched, to subtly change user interfaces all the time, and not only when absolutely needed to implement a feature of such importance that it warrants it.

From talking to many users over many years I can tell you that there is about a 50/50 split between people who like the changes you mentioned and people who dislike them. Which is why 1) these changes are optional, 2) the team is planning to introduce a softer rollout of such changes giving people a first-start dialog to make a decision on new UI options (see e.g. Blender or, more recently, Inkscape).

As a general issue, that's true, but in GIMP's case, every single major thread about it gets complaints about its UI. So it makes sense of updates focused on that; one might not agree with the specific UI decisions they take - UI/UX is unfortunately subjective like that - but any systematic attempt to improve the UI would make a vast difference to the value of the application.

UI in any moderately successful project is kind of like the dog and stick “No take, only throw!” Problem.

We want the UI to improve, but also the UI must never change.

I've been getting random crashes from Gimp lately, so it's nice to see a bugfix update. Let's hope my issues go away!

Unfortunately, it looks like this long-standing bug hasn't been fixed: https://gitlab.gnome.org/GNOME/gimp/-/issues/3104

That one is really common and really annoying.

At my job, we've been experiencing the massive XMP metadata problem, though not in GIMP specifically. In a rendering system built with Python, Pillow, and PyCairo. It took me a while to figure out why Pillow and PyCairo were crying about certain images. Turns out art we are receiving from a client, who uses Photoshop to make the art, when saved to a PNG, is un-openable with the default settings of (either Pillow or PyCairo, can't remember) as it expects metadata in the kilobytes, not the megabytes. Especially not in the tens of megabytes.

In some cases, we had files where the PNGs would be 90 MB at only a meager resolution like 800x600 or something, and when we figured out what was happening, and removed the XMP metadata, it shrunk down to 0.5 MB. Unbelievable.

Glad to see at least the GIMP team is on top of it. According to forum posts going back years, Adobe couldn't care less. Another reason to take FOSS apps over proprietary, any day.

finally support for webp?

GIMP has been supporting WebP natively since v2.10 release in April 2018.

Reply on news.ycombinator.com