Judging by images like these, today's business class is pretty much what economy class used to be in the 70s. Some argue that flying has become too cheap. I beg to disagree: flying in a humane manner has not become cheaper, it's just that you'd have to book business class nowadays.

... to what Tor already leaks, is the previous hop from which the exit traffic came, and possibly meta data on other tunnels relayed by (but not terminated at) the node. If the relayed connection is SSL/TLS encrypted, that encryption is end-to-end from the original client to the server; sniffing some exit-node memory does not help you there. If the related connection is in the plain, then, well, then sniffing the exit node's memory does not tell you any more than you already knew by looking at its plain-text traffic.

Now, Heartbleed is not completely harmless here: You may, if you're very lucky, be able to sniff the previous node name, but as Tor tunnels are longer than that, that does not help you much. Plus, tunnels endpoints tend to change every couple of minutes, making the cross section even smaller. Also, you may now be in a position to sniff data from nodes whose ISP network you do not control, allowing you to do network-wide attacks. That may in fact be the biggest problem.

...somehow did not make it into the summary:

Strandbeest is Dutch for Beach Animal.

One map that visualizes the non-uniformity of US population density pretty nicely is this one.

It does the same thing, for years on end, without having to take vacation days. The funny thing is that you do actually get used to it; I was a night owl, but not anymore. Now, if I do sleep in, I actually wake up with a headache.

... this should be in addition to good coding/style standards, proper design, proper source revision control, proper code reviews, and continuous testing/integration. Without any of the former, using this tool does not provide that much information: You first want to know whether your code does what you think it should do, whether it is thread safe, whether it is leaking memory, etc., etc., etc.

I agree with the power-consumption part, but the reason I would still not buy the Atom line is the simple fact that they do not support ECC RAM; when you say "reliability", you do want to know when your RAM walks out on you.

Supermicro sells a couple of mini-ITX board for mobile Core i7s, though, that will still allow you to build an under-30W-idle system with ECC RAM.

... because that is exactly what this initiative ("Buchpreisbindung") was aiming for. Protectionism is wrong, no matter what you name it.

Your average phone has a ~4 mm (diameter) lens. This yields an Airy disc of some 1.15 minutes of arc.

Even at a wide field of view (say, 60 degrees), this yields a maximum lateral resolution of some 3200 pixels. Isn't thus any camera with more than ~10 MPixels diffraction limited by the tiny lens, and not sensor limited?

So now with Chrome infecting my IE, I have no way to access vital corporate apps.

But you have: The Chrome-frame mode is activated only if one either prefixes URLs with cf: (which your corp. apps will not do), or if one includes a <meta http-equiv="X-UA-Compatible" content="chrome=1"> header in the HTML (or HTTP), which your corp. apps will not do either.

Only websites specifically designed to use the Chrome frame could force IE into Chrome-frame mode.