> People can be ruthless without being abusive.
Everybody has a different conviction about what is abusive and what is not.
Everybody has a different conviction about what is abusive and what is not.
"Of course, I'd also suggest that whoever was the genius who thought it was a good idea to read things ONE FCKING BYTE AT A TIME with system calls for each byte should be retroactively aborted. Who the fck does idiotic things like that? How did they noty die as babies, considering that they were likely too stupid to find a tit to suck on?"
But in real life, we have to worry about being honest. And it's honestly not true that anyone who reads a byte at a time is too dumb to operate a nipple. All it means is that whoever did it doesn't know much about syscalls.
> well-crafted insult
This is unnecessary vitriol directed at the person themselves as opposed to their code. It achieves nothing. He could get the same message across with far less words if he stuck to outlining the problem as opposed to attacking the creator of the problem.
I suppose Linuses appeal in this regard is similar to Simon Cowell or Anne Robinson off the weakest link. Sometimes you just like to see stupid called out.
This is entirely my conjecture and I have no way of proving it but I suspect Linus taking a break is Intel flexing its muscles on the Linux Foundation.
Not condoning his rants, like I say it’s ultimately upon himself these reflect badly, and they probably do little to stem the flow of incompetence ...
Until you realize it was you who checked it in. If you write enough code, you will eventually not write the best code for some situation. It could be because you were tired or you simply didn't understand that part of the code well enough. Instead of attacking someone with insults, it's better to understand why the code got written and work to not have similar mistakes made in the future. Remember, everyone here is on the same team trying to make the best piece of software possible. Berating teammates (which is really what is happening here) does not make them better teammates or make the team as a whole better.
The most egregious errors made in my experience and often Linuses, are by people who don’t see themselves, or have no interest in being “part of the team”. Who dont abide by the code quality guidelines, who have been told time and again, or who are trying to make weasel changes to subvert the organisation of the code to their own ends.
Linuses way, however isn’t really the most productive approach, Aine these kinds of individuals don’t care anyway. It sounds as though this new “code of conduct” might be an attempt to move things forward.
This line of thinking is a fantastic way to create a non-inclusive group.
> if you want to make a mess of things in your application you can do so without bringing down the whole system
You don't need an exclusive community to make that work. We as an industry have tools: fuzzers, testing frameworks, better programming languages and type systems, and proof assistants, all of which will do a better, more consistent job of ensuring quality than project leads being assholes.
Maybe he needs a creative writing hobby of some sort as an outlet to help keep such glorious color out of his professional emails. (I'm totally serious and would email him the suggestion if I didn't think it a waste of time because I don't know the man, he doesn't know me, yadda.)
Modern assembly languages - for processors that have SIMD or AVX instructions - are more natively able to deal with several things at one time than C is.
There are several cases where Linus went way over the top with insults, but throwing him under the bus because of that statement is ridiculous.
That's the whole problem with these CoCs, if people get to apply the most uncharitable interpretation of any statement, we can't have anything but extremely formalized conversation, lest we run the risk of getting kicked out because someone who doesn't like us misrepresented our words.
Bad code has a cost associated with it as well, it takes time to reject it, explain why it's wrong, and deal with the frustration of someone less experienced. Unfortunately with some developers they want to push that off on the person writing the code and bear none of the burden.
I've seen the costs of the latter in open source projects I've worked on. People who feel encouraged stick around, support the community, and when given good feedback will often learn from it and submit better patches. Taking the time to communicate and make sure everyone feels included is part of the cost to get that.
It's not a "harsh statement", it's a joke. If anything it's flattering of that person's stature.
> While it's pretty easy to say, yes he's not suggesting physical abuse, the statement implies this guy is not going to cut me any slack, I can expect to get verbally attacked for missing something in my code, etc.
I don't think it implies that, but that's besides my point. The remark was represented as "advocating physical intimidation and violence", which given the actual context is basically libel. You're free to interpret anything you want about the personality of Linus from him making such jokes, but misrepresenting it like that in public is dishonest and harmful to discourse itself.
https://arstechnica.com/information-technology/2013/07/linus...
The preferred pronoun of that person is currently "they":
https://en.wikipedia.org/wiki/Sage_Sharp
You may want to edit your post accordingly.
Correct. That means that you should, if possible, 1) try to communicate in a manner that most people won't consider abusive 2) adjust to the individual when needed. All of which Linus is saying he wasn't doing.