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.
> Does it mean that to share criticism you must be able to build it?
No. I've reported a lot of tickets/feature requests for a lot of projects that seemed to be taken good.
But criticism that seems entitled is rarely appreciated, and surprise about some obviously, severely underfunded project missing features is not very impressive neither.
There is a shitload of other missing features OP could have mentioned on this anniversary post and I guess it can feel a bit depressing too. "27 years! Happy birthday! Still no job though?". Eeh.
You can express constructive criticism with some humility.
"It's a shame nobody has been able to work on adjustment layers and layer styles, which are important features in such a piece of software."
OP did not feel entitled to me, but I can understand who their message could have been taken somewhat badly.
I appreciate what you’re saying. Do you mind if I dig into something a wee bit? Because us engineering types are often a bit communicatively tone deaf.
What specifically in the comment suggests a sense of entitlement? For me, I see none. I see a, “as an expert user, it’s surprising that such an important feature has been missing forever and I would like to criticize that.”
Edit: I’m not allowed to reply to your response but thank you for taking the time to respond.
Whoops, I edited to state that OP didn't feel entitled to me in the meantime. Sorry for this. It's more the "surprise about some obviously, severely underfunded project missing features is not very impressive" part. To be clear, I'm almost 100% sure the OP comment was written with good intent.
I don't work on the Gimp, I've read developers working on it at length, I think as a developer reading this comment I would be thinking "Well, we do what we can". Jehan, who wrote the post, contributes to the Gimp thanks to donations to his Ze Marmot project, his team cannot pay itself very well. They are going out of their way improving the Gimp anyway, indeed prioritizing features they need the most most certainly. But you can do only so much.
It might just be a matter of form/formulation. But it matters, because people won't take the time analyzing a comment for several minutes to completely put themselves in the commenter's shoes.
edit: you can respond by clicking on the "X minutes ago" link I think, but I saw your edit :-)
It was a suggestion, another suggestion is to fund gimp development. Another one is to move to a different tool. But to question on what is talking their time for my feature x to get complete is really not a polite way of discord on Open Source software.
The tool is free, so you are free to use it, and you are free not to. That is up to you. If you want a feature, please support the development woth either you cash or skill. Its that simple.
Unless you are ideologically inclined, it would be a better use of your resources to just pay for photoshop. As much as it angers people on this website, the subscription model provides a constant stream of funding that has gone in to keeping the tool the best on the market and for anyone using it professionally, it delivers far more value than it's cost.
I bought Pixelmator Pro for that reason. It's smaller than PS, it has great usability, no cloud-based subscription model and it's not Adobe but a small indie company.
This attitude is why no one seriously suggests GIMP over Photoshop.
Why would anyone with the talent required to do that invest time in a project that hasn’t been able to add these basic features.
Cloning the current GIMP feature set into a modern and competent system is easier than trying to work with the team that can’t ship these features alone.
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.