4 ms·

I've said this before (kinda) and I'll say it again: if you're not happy with a feature in an open source piece of software then get involved with the developme

I've said this before (kinda) and I'll say it again: if you're not happy with a feature in an open source piece of software then get involved with the development process: https://www.gimp.org/develop/ https://www.gimp.org/develop/ . If you don't know how and/or are not interested in learning then use another piece of software.

nkkollaw 8y ago
Yes, unfortunately I have no idea about GTK and similar. It seems unlikely that I would be able to learn, too.
- chappi42 8y ago
  In that case please try to be polite at least. Your answers (in the linked conversation) really don't feel ok. Why not, maybe, think again and, maybe, apologize?
  - nkkollaw 8y ago
    I don't think I was impolite, was I impolite?
bb88 8y ago
> if you're not happy with a feature in an open source piece of software then get involved with the development process This is a red herring. There's no requirement to participate in a group in order to give criticism of it. People often lack the time, skills, or political will power to change the direction of a open source software project.
- soperj 8y ago
  >People often lack the time, skills, or political will power to change the direction of a open source software project. And yet they still want to criticize people who provide free software.
  - bb88 8y ago
    That's reductive. You can't have free-as-in-speech (libre) software, if you're not willing to accept criticisms of it.
    - soperj 8y ago
      There's a vast difference between criticizing the software and criticizing the people who develop it.
      - bb88 8y ago
        So you're arguing for authoritarianism here. If you can't criticize someone, that's not free software development.
        jenscow 8y ago
        And the critic should also be open to criticism.
        jononor 8y ago
        Criticize actions, not the people making them.