Such aggressive tone, no need, very off putting and unconstructive. If I was considering employing the author and came across this article I'd be seriously put off despite the fact he clearly knows a thing or two.
One of those is irrelevant and the other one is false.
There's a lengthy, clear description of a problem, with a use case, leading up to a feature request...how is all of that "unconstructive"?
In fact, what's definitively unconstructive is the way the feature request is closed: dismissing the use case as invalid, despite the fact there's a description of the rationale behind it in the comments.
To clarify, the aggressive tone is non-constructive, as in it detracts from the article. You're right he makes a constructive point but I bet a bunch of people don't bother reading that far.
So what if the tone is aggressive? It's a venting piece. It says so in the second paragraph. Who cares if people bother reading it? Where it mattered - the actual github request - the tone of the discussion is right on point.
People who ignore the point to come here and complain about the tone, also further detract from the point.
FWIW, I find it extra hilarious that, in the context of employment search, I would form an opinion based on how - or what - a person _vents_.
One of those is irrelevant and the other one is false.
There's a lengthy, clear description of a problem, with a use case, leading up to a feature request...how is all of that "unconstructive"?
In fact, what's definitively unconstructive is the way the feature request is closed: dismissing the use case as invalid, despite the fact there's a description of the rationale behind it in the comments.