Live data from Hacker News

GIMP 3.2 released

gimp.org

91–92 of 92 posts

Re: GIMP 3.2 released

#91
post #90
post #80

Earlier quoted context omitted.

I guess I'm nobody then. I write code exclusively in vim. Unless you want to pretend that ctags is a proprietary version of an LSP, I'm not using an LSP either. I work at a global tech company, and the codebase I work on powers the datacenter networks of most hyperscalers. So, very much a real project . And I'm not an outlier, probably half the engineers at my company are just raw dawgin it with either vim or emacs.

Ctags are very limited and unpopular. Most people do not use them, by any measurement standard. Using a text editor without LSP or some form of intellisense in 2026 is in the extreme minority. Pretending otherwise is either an attempted (and misguided) "flex" or just plain foolishness. > probably half the engineers at my company are just raw dawgin it with either vim or emacs Both vim and emacs support LSP and intell…

[dead]

Re: GIMP 3.2 released

#92

Earlier quoted context omitted.

Yes, it's planned for transform tools and already possible with filters. Technically our transform tools are already capable of this (they use GEGL operations the same as our non-destructive filters). We just need to tweak it to not immediately commit the transform, and then implement a UI.

When does the final calculation happen then, at file save/export? Will be unexpected. Or does it end up in the final format? That's going to be a nightmare, because then you can't use GIMP to redact data anymore.

That's up to you. Right now filters work the same way - you can merge them automatically on creation, merge them at some point while working, or merge them on export. For formats like PSD, we'll eventually add the option to export as non-destructive filters as well.

We don't want to take away choices - we just want to add more options for people's workflows.

Post reply on HN