> one has to wonder if they ever use GIMP to do any realworld image editing at all
Like i said, the feedback loop with actual artists has tightened in the past years, especially with ZeMarmot project becoming real active in development.
> first and foremost they need to employ an ergonomics expert on their team.
Well "employ" may be the problem. I believe there's two or three contributors who will accept donations, but nobody is actually employed to work on GIMP full-time. If you know of ergonomics experts who'd like to contribute some time to a free-software project, or can produce a full-fledged UX audit for a few bucks, i'm sure that will be of interest to GIMP people.
> I've lots more instances of GIMP problems but this is not the place to raise them.
Maybe not, but thanks for taking the time to point out two downsides (slowness, and removal of a feature that's key to your workflow). Hopefully you can find time to contribute to the project: identifying hot/slow code paths doesn't have to be very complex but is very workflow-dependent so a report of yours can be very useful for optimization purposes.
As for the fade option, i have no idea what this debate was about. Please don't hesitate to post links to blogposts or tickets in the future.
Like i said, the feedback loop with actual artists has tightened in the past years, especially with ZeMarmot project becoming real active in development.
> first and foremost they need to employ an ergonomics expert on their team.
Well "employ" may be the problem. I believe there's two or three contributors who will accept donations, but nobody is actually employed to work on GIMP full-time. If you know of ergonomics experts who'd like to contribute some time to a free-software project, or can produce a full-fledged UX audit for a few bucks, i'm sure that will be of interest to GIMP people.
> I've lots more instances of GIMP problems but this is not the place to raise them.
Maybe not, but thanks for taking the time to point out two downsides (slowness, and removal of a feature that's key to your workflow). Hopefully you can find time to contribute to the project: identifying hot/slow code paths doesn't have to be very complex but is very workflow-dependent so a report of yours can be very useful for optimization purposes.
As for the fade option, i have no idea what this debate was about. Please don't hesitate to post links to blogposts or tickets in the future.