Cooling in arctic is cheaper than cooling in nevada desert.

Are you sure? In ether case, you're pumping water all over the place, and the Nevada desert is arid enough that if you just let air pass through that water it'll evaporate and cool pretty damn well (which is what all these big-name datacenters do for the bulk of their cooling). Humidity (not temperature) is the main impediment to evaporate cooling.

You don't pay for any of the Android stuff, you pay for a device which can run it and then you get it. Sure, you can easily pay for software, but you're not paying for the basic functionality. All of that is gratis. At worst you go to goo and get the gapps for your device, and maybe twiddle build.prop such that you can actually use the store, and then google will happily treat you the same as any other user.

Since you're not paying for Android, Android is not a consumer product. It's not like Windows where you can get it free or you can pay for it; you can only get it free. Perhaps there's some for-pay Android-on-PC efforts by now, I'm not sure. But community replacements for official software stacks are generally donationware and nobody has harassed me for money yet.

I'm substantially more upset about the Mycon, who are occasionally hostile no matter what you say to them. Watch those spores...

We're operating on borrowed time with this many unemployed.

It was perfectly innocent on that front until you suggested it might be otherwise. There's no shortage of men who love to throw money around. Were you going to mention shoes or something?

Let's take a look at why that is not smarter. You are throwing away the energy density and quick charge properties, and increasing complexity by adding, most likely, another entire charge controller. As well, there is absolutely no need to use an array of supercapacitors, because supercapacitors are the solution to the problem of needing an array! They have fast charge and discharge, they already act wide and not just deep.

You're throwing away energy density by wasting space on having two power systems, and you're throwing away quick charge by including a power system without quick charge. You'll want a separate charge controller for the separate power system, and that means still more efficiency loss and still more cost. It just doesn't make sense.

The issue is that what is complaining about isn't really private information. Yes, the page he is entering the info into is https, but that doesn't mean everything on that page is private info. It is secure page to prevent man in the middle attacks for things like credit card numbers. Your name and address are not at all private information and can be found out in any number of public records (including telephone books). Just because my favorite type of ice cream is sent to someone on a page that is https doesn't make that information private. Hell, I can use https to post things to Facebook for Bob's sake. Should Facebook then be forces to treat that all with the same security as my password?

That is not even close to true. Many of them were instituted as exceptions to aid the war on terror. The problem is deeper than the war on drugs; as terrible as that is, it is actually a symptom.

Intel will "solve" this problem by simply abandoning the old processors. They did it to the first atoms already; preview releases of new Linux distributions that Intel has contributed code to (e.g. Tizen) don't support them already.

ARM cores are dual-issue now, so that's just not that exciting any more.

Straw man, or at best, you failed to understand the argument. The argument is not that register renaming has a negative impact on cpu performance, the argument is that having more GPRs provides superior performance to register renaming. This is a proven fact; just recompiling some code for x86_64 provides a 15% performance increase for this reason alone (on the same processor.)

Kinda, true, no you don't, HAHAHAHA.

It's a good idea because magstrips are easy to erase and contacts are easy to destroy. It's unfortunate that this implementation is so crap, but that doesn't invalidate the concept.

Thanks for the heads-up! I will, in fact, wait. (I am getting an Ouya for the living room, but that's something else...)

And we should also all have better password management. If all we're providing now is a very small token (password) then we could be providing a larger token (uniquely generated certificate per machine login) as well and really getting something in the bargain. But if the user has to do anything to enable this, they won't. It ought to be in the browser. I'm not talking about SSL, which is good and all, but about the reverse basically.

The San Francisco plumbers' union was (is?) famously a Mafia operation. What's it like out there? Is he getting any kickbacks? Etc.