GIMP Turns 27
11–20 of 310 posts
Re: GIMP Turns 27
#12Still no adjustment layers, still no layer styles. It’s so easy to just critique away…but really? Really? Those are just absolutely essential image editing software features. What have they been prioritizing ahead of that?
And no macOS native gui ;_; It’s almost unusable in OSX because of that.
Re: GIMP Turns 27
#13Re: GIMP Turns 27
#14I can't fathom that to this day people present it as an alternative to Photoshop where it's little more than an unusable Paint.
I mean, photopea.com is free, developed by a single guy, and runs in the browser, and it's light years ahead of Gimp.
Re: GIMP Turns 27
#15Still no adjustment layers, still no layer styles. It’s so easy to just critique away…but really? Really? Those are just absolutely essential image editing software features. What have they been prioritizing ahead of that?
Its open source, so feel free to prioritise your own workload into making this feature.
Re: GIMP Turns 27
#16If they would just copy Photoshop... Even the 2000 version of Photoshop.
Re: GIMP Turns 27
#17Krita (https://github.com/KDE/krita | https://krita.org/en/) is a more intuitive UX imo.
Re: GIMP Turns 27
#18Still no adjustment layers, still no layer styles. It’s so easy to just critique away…but really? Really? Those are just absolutely essential image editing software features. What have they been prioritizing ahead of that?
> What have they been prioritizing ahead of that? There are very few active maintainers, what few there are have been scratching their own itches.
Re: GIMP Turns 27
#19The biggest stain on FOSS, with the worst apologists, 27 years strong! Try drawing a circle, in the year 2022.
Re: GIMP Turns 27
#20Still no adjustment layers, still no layer styles. It’s so easy to just critique away…but really? Really? Those are just absolutely essential image editing software features. What have they been prioritizing ahead of that?
Its open source, so feel free to prioritise your own workload into making this feature.
Does it mean that to use a tool you must be capable of building it?
Does it mean that to share criticism you must be able to build it? I’m thinking about applying this logic to the rest of life and it’s rather amusing to imagine the silence. Hmm, maybe that wouldn’t be so bad.
I think one could more fairly say, “offer up money for someone to build the features you need” but I think that’s also a very difficult proposition given the logistics of the matter.