People who survive rape sometimes have Post Traumatic Stress Disorder (PTSD), which includes an extreme sensitivity to anything reminding them of their experience (like a rape victim who later sees a rape scene in a movie). There's a growing consensus that, in some circumstances, warning people of potential triggers is considered polite, at least, to give them a chance to avoid it.

You're not rude, but you are ignorant. The variant of pancreatic cancer that Jobs had was much more survivable than the majority case, and his nine-month fruit juice odyssey contributed directly to an early death; had he immediately followed the proper medical advice for treatment, he'd almost certainly still be alive today.

Well done! Now do the Enterprise E against an Imperial Star destroyer.

Wow... First time I've seen a callout to 2 PPCLI over Kapyong. Definitely a high point in Canadian military history.

Because NoSQL isn't an alternative to an RDBMS except where an RDBMS is a bad choice in the first place. They're complementary technologies, doing well what the other doesn't. If you're appropriately set up with MySQL (or Postgres, or Oracle), then any NoSQL solution will be a bad move no matter how mature.

Besides MySQL, MariaDB and Percona, there's Dribble that's actually a viable fork. One's official, one's competing by the original founder, one's got all the experts at clustering, and one's just kind of there as well. So now, instead of one weak-ass database, you have four that are mostly the same but not identical, which will bite you in the ass at some unspecified point in the future.

Back when it was just MySQL, it was a reasonable choice because it had known strengths and weaknesses. Now you've got shitty fragmentation. If you're starting a new project, which fork do you go with?

Easy answer: Postgres.

If you sell to one tech company, you're buying into subsequent sales of that tech company. Acquisitions happen all the time--Oracle buying Sun surprised no one, and Widenius didn't give a shit because he got a big payout. Now he wants to repeat it.

MariaDB is Monty Widenius' fork after leaving Oracle. MySQL is in Oracle's hands in the first place because Widenius sold MySQL to Sun. The man responsible for MySQL is also responsible for the fragmentation of the community into a bunch of forks with growing incompatibility problems.

That's not what you said. You said "whatever O wants, O gets". If that were true, he wouldn't need ninja negotiating moves like "ask for $100, settle for $10". He wouldn't have to negotiate at all. Coming along afterwards and saying "O didn't get what he said he wanted, but what O got, is what he really wanted" is just bullshit.

Haters gonna hate.

Gotcha: taxing the rich won't cover spending, so don't tax the rich. That's smrt.

And yet, the U.S. went over the fiscal cliff, clawing back only at the last second. And only be delaying the debt ceiling fight for several weeks. Do you think that's what O wanted? Of course not. He wanted a grand bargain, and didn't get it. So where's his omnipotence now?

I think the point is that, if you're asking for "advantages", you're implicitly accepting the respondent's subjective judgement on the matter. To dismiss his answers as wrong for failing to match your subjective judgement is, I'd say, pretty much the definition of No True Scotsman.

Though I agree with you that whether or not those are real advantages is arguable :)

I can appreciate the irony, but I dispute it: He was asked for three advantages, and on naming three, told "those aren't real advantages". Isn't that a 'no true scotsman'?

The name of the fallacy you just demonstrated is "No True Scotsman".

So, to be clear as to the outline you present: Mauro made one ill-advised comment on the bug, and Linus shit all over him? No "Mauro, you're wrong and here's why", no "Hey Mauro, you need to remember that we don't break userspace apps, regardless of where we think the bug lies". Just zero to SHUT THE FUCK UP.

That's the problem here: Not that Linus corrected Mauro, but that he exploded in a rage. A more temperate response would have resolved what really was ultimately a miscommunication.

BTW, you leave out Mauro's longer, more detailed response for where he lays out a good case for understanding whether or not there's a userspace bug in play because it explains why the tests didn't find the regression. Linus assumed Mauro was passing the buck; Mauro was actually trying to track down where the process failed. But that doesn't matter, does it? We're geeks, we're socially efficient. And if Mauro now has a giant black mark of Linus shitting on him, well, it doesn't matter if Linus was right because that's how we roll, and the rest of the world is wrong.