I remember my car broke down, it was trash worth maybe 200 in scrap metal at the time. The tow to the yard was like 100 or something. I was screwed and couldn't get rides to work. My buddy lent me a car he had for free. I did not complain once to anyone about the things wrong with that car, and I never will. I even fixed some small issues with it to return the favor. The guy and that car saved my livelihood at the time.
I realize that's a little dramatic. I also think people are allowed to raise issues. But the entitlement and the way people talk about free software is annoying. Especially when alternatives cost as much as a used or new car.
If you have a Ferrari pallete for software then I hope there's an alternative that satisfies that for free, if so say so, otherwise shut up, contribute, or pay the Ferrari dollars already.
Eh. I draw the line in a slightly different place. I think saying that some piece of software is bad is not an attack on the developers. It doesn't imply ill will, or entitlement or any of that. People are allowed to write whatever software they want. And its generally net positive to share that software, for free, with the world.
These things are true at once:
- Good work inkscape developers! Inkscape is used by lots of people. I'm happy for the developers and the users, and I hope inkscape keeps getting better.
- I don't want to use inkscape because when I tried it, it seemed ugly, slow and buggy.
The only problem here is when people equate "this program is junk" with "this person is junk". That's a very dangerous belief to have, because it makes an enemy out of practice. And an enemy out of experimentation. The road to expertise is paved by mistakes. If bad quality work makes you a bad person, you can never learn a new skill.
I think you are right. But I also know what it's like to be on the other side of it. Taking it personally isn't the big issue.
Instead of celebrating a release the top comments are things like "this one thing doesn't work therefore trash, and unusable". Which reads like coercion for the devs to go spend a bunch of time and prioritize their life to satisfy someone at the free all you can download buffet.
The thing that sucks about it is. The devs will go fix that thing. Make a new release. Then the top comment will be some other bug, because all software has them. Then if there are no bugs it will be something else like the devs cousins dogs affiliation the the neighborhood cat. It just gets old to me.
I know what its like to be on the other side of it too. I've had plenty of things I've done posted to HN over the years. I've gotten all sorts of comments.
Honestly, I'm chuffed and always a little surprised when people read what I've written, or when they like my work. If someone says your software has a bug, that means they liked what you're doing enough that they took time out of their day to try it out. It means they care about the problem you're solving enough that they want you to fix it.
I'd take criticism every day over getting no response at all. Criticism of features means you're solving a problem people care about. If the feature they criticise is obscure, it means all the other features are working better.
I don't know if that point of view is teachable though. Even knowing all that, I feel criticism incredibly acutely in person. Stepping on stage and showing your work to a crowd is terrifying. But I think its good for us. It tempers us, somehow. Makes us more real.
I appreciate you