moot point. it will probably cost you nothing, because if you are running XP, you aren't buying this. If you are running XP, then you are buying a new machine and chances are it will come with either a recent OS or 10 itself.

People with old machines building their own new machines and getting 10 will be in the minority. Tip: get a cheap 7/8.1 license to upgrade for free to 10.

Jeep, as a brand, almost died simply for having non-round headlights.

Brand association is a powerful thing. Probably an evolutionary thing, actually; if it doesn't taste, sound or smell like what it's supposed to, it's not the same thing, so don't risk it.

What I mean is that it's a lot harder for someone who owes their job the the democratic process to argue this without comint across as a hypocrite.

The point to the vote wasn't to establish the science. It was to provide an argument to politicians that this issue is real. Poltiicians don't understand science so the argument they use is political.

A senator may well want to argue that the science is wrong. It's a lot harder to argue that democracy is also wrong.

Of course we don't like this. Slashdotters like science. Many of us are scientists. This is a terrible way of carrying on, but the important issue is we deal with the environment. If we need to back up our scientific argument with a political one, so be it.

If the American public truly believed, so overwhelmingly, or cared, Congress wouldn't have an incumbency rate of somewhere between 96 and 85 percent (depending on how you count.)

America doesn't have elected officials, they have an aristocratic class, and a few political dynasties.

Which can be rewritten as 'Microsoft specified it would only be free for the first year, which I interpret to mean that there will then be a yearly fee.'

The other, more logical, interpretation is 'After a year, even if running windows 7, 8 or 8.1, you'll need to purchase an upgrade at standard retail.'

The thing about a String type is that it's a common means of sharing data, but there are dozens of incompatible implementations. Qt uses QString, I remember using a regex library that uses a UnicodeSting type, and I've worked with more than one toolkit that uses its own custom string class. Mixing and matching these can be a headache.

Complex types are less of an issue because they're a lot more specialised. You're more likely to want to read a value from a widget input field, parse it using a regex and then use the result in a third library than to do the equivalent with a complex number. I'll grant you, this is more of a perceived problem with std::string than a fundamental issue with C++ but still, I rather like the fact that any Java library I use will use java.lang.String if it needs a string.

No built in string. Complicated templates mechanism. A lot of C legacy crud. Antiquated #import system (the main issues is that this can lead to horrendous build times). Not sure if these are better in D, but they are problems that it would be nice to address.