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.