3 ms·
I didn't find this rant abusive. Once worked for a law firm in a high stress industry - some of those lawyers were abusive, woah nelly. Also, have a brother who
by snomad 11y ago
I didn't find this rant abusive. Once worked for a law firm in a high stress industry - some of those lawyers were abusive, woah nelly. Also, have a brother who was in army, you can't even imagine the language of he and his friends.
This is child's play and someone who ultimately cares about delivering a quality end product who was offended by someone taking away from that mission. And his point was right, the code was bad and shoehorned into a magical one size fits all solution.
I'm most curious on the age / background of those in this thread who do find it hurtful and offensive.
- nabla9 11y ago>I'm most curious on the age / background of those in this thread who do find it hurtful and offensive. Me too. I feel that there is generational shift. For me, abusive means that someone picks you as a permanent target and treats you badly consistently. I'm completely fine with people calling me with names over some issues when it's clear that they are fighting against me over some specific issue. I'm allowed to use strong words as well. When the subjects changes, there is no hostility. That's how you know you are dealing with emotional person who is not abusing you. Picking up text fragments and analyzing one email for triggers that can be labeled as "abusive" seems so weird. I guess I feel that there is difference between "abusive language" and abusive and others don't see it.
- marrs 11y agoI agree, and I think you're both right that it's generational.
- tptacek 11y ago"the code was bad and shoehorned into a magical one size fits all solution" Can you explain what you mean by this? "Not idiomatically appropriate for the kernel" and "bad" are very different concepts. There's an interesting phenomenon happening where people are retconning Linus's objection to this code into a value judgement on the code itself. I'm curious whether that's what you're doing, or whether you have a grounded argument to back up your assertion that the code was, as you chose to put it, "bad".