That would be awesome.

It's just the photino birds.

Smug, arch, deliriously self-absorbed, and given to carrying around precious little pet dogs like he was some kind of eccentric Bond Villain. That he would pay Slashdot to interview him -- and that he would be so out of touch as to think there were any genuine tech decision makers left on Slashdot -- comes as no surprise at all.

Immediately you say? Android users might disagree.

QUIC has congestion control. (I suppose your brain would explode if you saw uTP, which runs over UDP yet is even less aggressive than TCP.)

I think Google intends to put it in the kernel once they have finished actually designing and standardizing it. Since it would take 10-15 years to get QUIC into the Windows kernel, they're putting it in Chrome as a stopgap.

QUIC uses an equivalent of SYN cookies to prevent some kinds of DoS. It also uses packet reception proofs to prevent some ACK spoofing attacks that TCP is vulnerable to. Overall it looks even better than TCP.

As for encryption, Google gives two reasons. They intend to run HTTP over QUIC and Google services are encrypted by default; it's more efficient for QUIC itself to implement encryption than to layer HTTP over TLS over QUIC. The other reason is that middleboxes do so much packet mangling that encryption is the only way to avoid/detect it.

He's including free speech in civil rights. He supports free speech for everyone except fanboys and trolls.

Caused by policies enacted during the Clinton and Carter administrations, which the Republicans had twice tried to repeal. The Clinton-era economic boom was the bubble rising; Bush and Obama inherited the bust.

Actually, the root causes can be traced back to FDR's New Deal, and probably further. No-one came out of that mess smelling like a rose, but trying to pin the blame solely on either Bush or Obama is simply short-sighted.

Yes. And one of the reasons for having hot spares (and replicas and backups) is the chance of multiple drive failures close together. So it's not a problem if you've planned things properly, but it's something you need to consider to create a good plan in the first place.

Depends a lot on the drive, but that can be a problem. The best solution is to either buy a drive with a significant amount of over-provisioning built in (like the Intel S3700 or Seagate 600 Pro) or over-provision it yourself. That means that when it fills up it still has plenty of spare area to remap blocks.

Enterprise drives typically have at least 20% over-provisioning; consumer drives can be 5% or less. A 400GB Seagate 600 Pro is the same as a 480GB Seagate 600, except for that setting.

Micron and Toshiba make them, but they're hard to find. You can also get SLC ioDrives. But the Intel S3700 looks to be nearly as good, and much, much cheaper.

Not off hand, sorry. I haven't been the sysadmin for 18 months (moved back to programming), and I don't want to give a guess that might be off by a factor of two.

Because if write wear is the prime failure mode and you're running RAID, you're likely to lose multiple SSDs in a relatively short interval.