Wait, you mean Nokia patented fractals?

Everybody knows that the US government intercepts the world's communications. If they now do the same to Americans, it just seems fair.

Unfortunately, at my job there isn't much tail to watch. :/

Oh, I hear you. I'm getting an engineering degree, and it's fucking worthless. The best I can hope for is to make a decent living while contributing to the fortunes of people whose life has been and will always be much better than mine.

Essentially, there are three tiers of skills in our present world. The gold tier is entrepreneurship. The people who have it become rich and rule the world. The silver tier is money-twiddling. These people may not be gold, but they are close enough to money that they get rich as well. Then you have nothing, and twenty levels down you have the shit tier, where all the other skills are. We techies can at best aspire to be kings of beggars.

Modern platforms have dtrace.

And that's where you're wrong.

Basically, it's like marrying a gorgeous woman. She looks really hot, but you can never just let your lust run wild, because she thinks too highly of herself. Every instance of intercourse must be bargained for, and you're lucky to get it once a week; and when you do, she just lies there like a dead tuna. Soon, you begin to question whether it was worth spending so much money and effort on her.

I don't like the LibreOffice application icon. It looks too much like a generic document.

They're way off. A life-sized horse would hold only one person, two at most.

I also use Chrome on OS X, and the big feature that enabled me to switch was Keychain integration. I used Safari before, and the ability to share passwords between the two browsers has been invaluable. This feature has been requested for Firefox years ago, but never delivered. Until it is, I can't consider it a serious contender on OS X.

A cubic millimeter is hardly "at the size limit that the human eye can see unaided". A fleck of dust is quite a bit smaller than that, and perfectly visible.

Also, from the FAQ:

Q: Doesn't HTTP pipelining already solve the latency problem? A: No. While pipelining does allow for multiple requests to be sent in parallel over a single TCP stream, it is still but a single stream. Any delays in the processing of anything in the stream (either a long request at the head-of-line or packet loss) will delay the entire stream.

This does not make sense. You're still using TCP, which is a reliable transport protocol, which means packet loss is dealt with at the TCP level, and not seen by SPDY. So the effect of "delaying the entire stream" is exactly the same as with HTTP. The only difference is that you're using fewer TCP connections (one instead of several - in fact, this is one of your selling points!), so the probability that a request will be affected by packet loss in an unrelated request *increases*: packet loss slows down all subsequent traffic on SPDY, since it's sharing a single TCP connection, while with HTTP it only affects traffic that uses the same connection (out of several).

In the real world, packets loss rates are typically 1-2%, and RTTs average 50-100 ms in the U.S.) The reasons that SPDY does better as packet loss rates increase are several: SPDY sends ~40% fewer packets than HTTP, which means fewer packets affected by loss.

But the packets are bigger. If packets are lost due to noise, increasing the size of a packet increases the probability of having an error within it. 10 dollars says you "tested" this in a simulation by fixing the probability of losing a packet, instead of fixing the error distribution. That's going to overestimate the improvements of having fewer smaller packets.

One year doesn't strike me as particularly slow, either. And what's the point of asking people to contribute now, when you've already designed and implemented your idea and put it in production? Isn't this the same Google that froze the WebM specification? Openness for standards is not the same thing as openness for source.