Yeah, those mailing lists used to have some quite funny stuff; my favorite so far is smth along the lines of “whoever thought this was a good idea should be retroactively aborted”.
But, on the other hand, damn it’s toxic. Should’ve really sucked to work on the kernel back then.
Someone else pointed out that he actually apologized for being toxic sometimes and took some time off as a kernel maintainer because of that. Nice to see.
He did hurt the mission. Plenty of kernel maintainers have left, and those were people who had been with the project for years. Losing experienced people to toxicity 1000% harms both the project and the product.
In almost instances of Linus going off on one in public it is because maintainers weren’t doing their jobs (to act as quality gatekeepers), or particular developers thinking they could steam roll road changes through if they kept submitting them, or not listening to what Linus was saying. I remember Linus used to ream out Hans Reiser a lot (the guy who was subsequently imprisoned for murdering his wife) because he constantly tried to get ReiserFS into the kernel despite serious issues Linus had with it.
So generally when you see a rant, there is a history behind it and the rant itself is directed with a point. I also think it’s self evident that the kernel has benefited from this “benevolent dictator” model. I’m sure some people have gotten all precious over their feelings being hurt. The rest raised their game and the result has been a code quality standard you’ll probably never see anywhere else.
I can understand Linus getting frustrated at people who consistently push him (i e. Lennart) and I agree that there’s a reason he’s stayed at the helm of kernel maintenance and development all this time; however, that doesn’t denigrate that this is an unacceptable way to treat someone which Linus himself acknowledges! If this were about ReiserFS going into the kernel, I would understand that. But a poorly made commit should not be met with this vitriol. I’m not saying there shouldn’t be consequences for poor work, but this is not it.
If there’s a surplus of talent (sounds like Mauro was dead weight) then at most he was just rude on Mauro’s way out the door.
I’m not saying it’s cool to be rude, but if it’s Linus’ review then you get what you get. To be butthurt about someone being rude to you should motivate you to learn your code interactions better. (In this case error handling)
You’re making judgements on people’s utility and ability based on the volatile reactions of man who admits to having issues. That creates toxic environments where people are not encouraged to do better, but any amount of change is due to fear of repercussions. This does not promote growth or new ideas that would genuinely improve something, but rather a fear of failure if they attempt something new. This also isn’t useful programming criticism because the actual useful criticism is buried in an emotional slurry that’s going to make something less receptive to the useful information.
You are just going to die on this hill, aren’t you? Even Linus recognized that his attitude was toxic, eventually, and that it was having a negative impact on the kernel development community. Yes, people left. Talented people decided it wasn’t worth the abuse.
You seem eager to pose this “if the product was undamaged” as if you can quantify what might have happened differently, but then in a comment below you ask someone else to prove that maintainers left.
It might shock you to learn that products are developed by people. Actual people stay or leave and work wildly differently based on things like respect, expectations, and being in a hostile environment.
Want proof of that? Go work on an actual project with a team sometime.
edit - And this isn’t even accounting for the ways toxic communication impedes wider adoption of a product
People who could be easily replaced. It’s a non issue.
I do work on software teams, and don’t conduct myself like Linus, because I’m not Linus. That pattern of communication isn’t available to me, an average engineer.
But if someone spoke to me that way (and they have) I took it as a clear signal I need to level up and act right. Not an invitation to feel bad about myself.
Linux has clearly not missed out on wide adoption in any way.
I was curious as I couldn’t help but laugh, but damn dude. That is rough. Hilarious looking at it now, but I feel bad for whomever was at the receiving end.
Of course, I’d also suggest that whoever was the genius who thought it was a good idea to read things ONE FUCKING BYTE AT A TIME with system calls for each byte should be retroactively aborted. Who the fuck does idiotic things like that? How did they not die as babies, considering that they were likely too stupid to find a tit to suck on?
Yeah, those mailing lists used to have some quite funny stuff; my favorite so far is smth along the lines of “whoever thought this was a good idea should be retroactively aborted”.
But, on the other hand, damn it’s toxic. Should’ve really sucked to work on the kernel back then.
Someone else pointed out that he actually apologized for being toxic sometimes and took some time off as a kernel maintainer because of that. Nice to see.
This happened on kernel 3.8, he stepped down on 4.18. That’s plenty of time time for as lot more fuckups.
It’s not really a fuckup it’s like a fucksideways.
The kernel was safe, only feelings were hurt
I meant Linus’ behavior was a fuckup. And he probably fucked up a lot between this example and his stepping down.
Was the product impacted? Did Mauro get his commit together?
If the product was undamaged he was just rude. A fuckup means he hurt the mission, he hurt his goals
He did hurt the mission. Plenty of kernel maintainers have left, and those were people who had been with the project for years. Losing experienced people to toxicity 1000% harms both the project and the product.
In almost instances of Linus going off on one in public it is because maintainers weren’t doing their jobs (to act as quality gatekeepers), or particular developers thinking they could steam roll road changes through if they kept submitting them, or not listening to what Linus was saying. I remember Linus used to ream out Hans Reiser a lot (the guy who was subsequently imprisoned for murdering his wife) because he constantly tried to get ReiserFS into the kernel despite serious issues Linus had with it.
So generally when you see a rant, there is a history behind it and the rant itself is directed with a point. I also think it’s self evident that the kernel has benefited from this “benevolent dictator” model. I’m sure some people have gotten all precious over their feelings being hurt. The rest raised their game and the result has been a code quality standard you’ll probably never see anywhere else.
I can understand Linus getting frustrated at people who consistently push him (i e. Lennart) and I agree that there’s a reason he’s stayed at the helm of kernel maintenance and development all this time; however, that doesn’t denigrate that this is an unacceptable way to treat someone which Linus himself acknowledges! If this were about ReiserFS going into the kernel, I would understand that. But a poorly made commit should not be met with this vitriol. I’m not saying there shouldn’t be consequences for poor work, but this is not it.
Did that demonstrably happen?
If there’s a surplus of talent (sounds like Mauro was dead weight) then at most he was just rude on Mauro’s way out the door.
I’m not saying it’s cool to be rude, but if it’s Linus’ review then you get what you get. To be butthurt about someone being rude to you should motivate you to learn your code interactions better. (In this case error handling)
You’re making judgements on people’s utility and ability based on the volatile reactions of man who admits to having issues. That creates toxic environments where people are not encouraged to do better, but any amount of change is due to fear of repercussions. This does not promote growth or new ideas that would genuinely improve something, but rather a fear of failure if they attempt something new. This also isn’t useful programming criticism because the actual useful criticism is buried in an emotional slurry that’s going to make something less receptive to the useful information.
You are just going to die on this hill, aren’t you? Even Linus recognized that his attitude was toxic, eventually, and that it was having a negative impact on the kernel development community. Yes, people left. Talented people decided it wasn’t worth the abuse.
Yes people left and were not heard at the time:
*https://sage.thesharps.us/2015/10/05/closing-a-door/
*https://mjg59.dreamwidth.org/38136.html
You seem eager to pose this “if the product was undamaged” as if you can quantify what might have happened differently, but then in a comment below you ask someone else to prove that maintainers left.
It might shock you to learn that products are developed by people. Actual people stay or leave and work wildly differently based on things like respect, expectations, and being in a hostile environment.
Want proof of that? Go work on an actual project with a team sometime.
edit - And this isn’t even accounting for the ways toxic communication impedes wider adoption of a product
People who could be easily replaced. It’s a non issue.
I do work on software teams, and don’t conduct myself like Linus, because I’m not Linus. That pattern of communication isn’t available to me, an average engineer.
But if someone spoke to me that way (and they have) I took it as a clear signal I need to level up and act right. Not an invitation to feel bad about myself.
Linux has clearly not missed out on wide adoption in any way.
I was curious as I couldn’t help but laugh, but damn dude. That is rough. Hilarious looking at it now, but I feel bad for whomever was at the receiving end.
Gold
That’s some quality venom.