The tricky thing is, long posts like this tend to provoke responses selectively nitpicking about one thing, and then either going way down into the definitional weeds or galloping to the next nitpick without acknowledging any error.
I think the long content is fine as it stands, but it isn't necessarily a good seed for discussion in a comment thread (as opposed to an underlying article).
> provoke responses selectively nitpicking about one thing
I'd say that's where the community is made. Either the community supports this type of behavior or not.
I'll at least say I sometimes downvote opinions I agree with and upvote opinions I disagree with. That's because I don't see the upvote and downvote as a signal of my personal feeling about the comment but rather about how I feel the comment should be placed in ordering. Sometimes I downvote a comment I agree with because it is a bad argument and I want to discourage that behavior. Or because it is just signaling or ignores the parent. Sometimes I upvote bad comments because there's a conversation I want highlighted. Sometimes because despite it being bad I think they bring up good points others are ignoring.
But I think we can have more in depth conversations on HN. That comment was much longer than I usually write (and I'm wordy) but I think it is a matter of what we want as a community. For example, I always downvote oneliners, memes, or when someone is just trying to dunk on the other person.
I think the long content is fine as it stands, but it isn't necessarily a good seed for discussion in a comment thread (as opposed to an underlying article).