> Please... Do you really think that upon reading my comment the author going to assume the foetal position and cry?
I'm not sure about the GP here, but my original reply was not because I thought you were hurting someone's feeling, but because ultimately it seemed inaccurate. I looked through the project README before commenting, and what was obvious is that the author does know how to use the command line, so I tried to keep my comments relevant to the point.
The README contains aliases, redirection (both truncating and appending), multiple pipes within a single command line, and ultimately, within a reproduction of the output of the --help flag an example of piping curl to this command.
Ultimately I found your original comment inaccurate. I find comments that are style over substance, especially when that style is used to denigrate an individual, rarely useful.
> Children in my school used to use the phrase "that's harsh!" upon certain remarks from other children. And do you know which part cut the deepest? It was the "that's harsh". Why? Because it is a double attack on me. It both acknowledges that was said is true and adds that I am too weak to handle the attack myself.
Saying "That's harsh!" doesn't itself imply accuracy to the statement. Just the opposite, in fact, since it's an acknowledgement that the parson went a too far. The delivery, on the other hand, can change the meaning entirely, and I think that's what you are referring too.
That said, I think you're mistaken to equate my use of it to this past experience of yours. I obviously wasn't saying it in a way like "Ha, sick burn!", but instead "I think you've overstepped in a way that hurts your point, if your point is valid at all".
> Are you projecting your insecurities on the author?
It's interesting that you included this, as I think you're perhaps projecting some insecurities from your own past onto some of the statements being used here. At a minimum, your own words have brought that possibility into the discussion.
I'm not sure about the GP here, but my original reply was not because I thought you were hurting someone's feeling, but because ultimately it seemed inaccurate. I looked through the project README before commenting, and what was obvious is that the author does know how to use the command line, so I tried to keep my comments relevant to the point.
The README contains aliases, redirection (both truncating and appending), multiple pipes within a single command line, and ultimately, within a reproduction of the output of the --help flag an example of piping curl to this command.
Ultimately I found your original comment inaccurate. I find comments that are style over substance, especially when that style is used to denigrate an individual, rarely useful.
> Children in my school used to use the phrase "that's harsh!" upon certain remarks from other children. And do you know which part cut the deepest? It was the "that's harsh". Why? Because it is a double attack on me. It both acknowledges that was said is true and adds that I am too weak to handle the attack myself.
Saying "That's harsh!" doesn't itself imply accuracy to the statement. Just the opposite, in fact, since it's an acknowledgement that the parson went a too far. The delivery, on the other hand, can change the meaning entirely, and I think that's what you are referring too.
That said, I think you're mistaken to equate my use of it to this past experience of yours. I obviously wasn't saying it in a way like "Ha, sick burn!", but instead "I think you've overstepped in a way that hurts your point, if your point is valid at all".
> Are you projecting your insecurities on the author?
It's interesting that you included this, as I think you're perhaps projecting some insecurities from your own past onto some of the statements being used here. At a minimum, your own words have brought that possibility into the discussion.