[shevy-java]

> The problem is a shortage of developers to address them.

> So if you can, contribute.

Well, that requires knowledge of C. That already excludes like 98% of the user base or so, or perhaps 90%.

Also, even aside from this, if a majority wants feature xyz but you don't like that, what can you do? It is a constant time investment to convince a majority that what they want may not be great.

You make it sound as if the only bottleneck is lack of developers. I think there are many more bottlenecks than merely lack of developers.

[Fogest]

Agreed, I think the bottlenecks are often the gate keepers already in the community. In fact one of the other replies to the parent indicates that mentality. Where they are happy that GIMP has remained unchanged and are happy with the UI. This is exactly the kind of sentiment that often makes progress become stagnant. The small vocal community gets used to things like poor UI, and then turns into a NIMBY about any changes that would benefit the masses (but require them learning new things).

Unfortunately I think this is why most of the time you don't see progress in applications like this until there is a fork or a whole new application. Especially with AI based development now, I think the problem is often not the lacking people to make code, but lacking people that allow the code to be contributed in the first place.