There is much less swearing going on than in the last few rants. Usually that means Linus is extra serious.
I remember reading a chef (might have been Bourdain) who said something like when the head chef is shouting "Where the fuck is the fucking lamb you useless piece of shit" then things where basically on track, but if he calmly said "can you please hurry up with the starters for table 6 and 7" then he knew he was in deep trouble and really had to pick up his pace.
Did we read the same text? I didn't read it as exploding, but just as a teacher teaching the pupils about the rules of kernel and what not to brake. The text was very clear and informational.
I definitely read it as exploding. It's not what you do, it's how you do it. Swearing (even if partially censored) and capslock are bound to result in a negative emotional reaction from the target, which will only make the target resent you, regardless of your justifications.
Even Linus recognises that "I just go ballistic" a bit later in the thread ;-)
I read it as exploding. The post above yours was deleted when I saw yours, so I won't defend it, but share hire I read Linus's update.
I believe the exploding appearance was an intentional writing style. We reading it because a) it's Linus and b) he very clearly communicates his position to the point of being crass.
It works and is stated in the opening: "Dammit. I haven't had to shout and curse at people for a while, but
this is ABSOLUTELY THE MOST IMPORTANT THING IN THE UNIVERSE WHEN IT
COMES TO SOFTWARE DEVELOPMENT"
Makes a clear statement AND expresses a clear tone. Was he teaching? Yes. Did he make his point? Yes. Was he calm? Behind the keyboard maybe. But in the email I'd wager he didn't want to look calm
I agree.. people can be dishonest and hurtful while being perfectly polite, just like they can be honest, kind and caring while swearing like sailors. That is the difference that matters. When you ignore that and just look at the form, you get https://en.wikipedia.org/wiki/Perverse_incentive
Here's Linux talking about being straightforward, and why he cannot afford ambiguity:
This made me laugh, then cry. I regularly hit kernel regressions in functionality (e.g. worked and now doesn't) in both my personal and professional/work systems. Sadly, the components are not niche drivers, it's things like ath9k, i915, iwlwifi, alsa (and several drivers there), etc. The kernel desperately needs more testing than just a handful of developers dog fooding it before calling it 'good.'
I don't understand why this is so interesting, as it doesn't seem to be anything about regression per se.
A userland tool supported functionality that it can't anymore, because it isn't available in a new kernel. This is not surprising, as people find ways to access and change data outside of published APIs all the time and they get patched away. The userland author said that the kernel upgrade would break old versions of the tool. So what?
edit:
More interestingly, he later explains his behaviour (and sort of apologizes for exploding): https://lkml.org/lkml/2018/8/3/727