Great. Now every website hacking attempt would be called "going rogue". All "roguelike" discussions will be censored and prosecuted. And God help you if you are found in possession of a certain amulet...

Well, duh! You're using the 32-bit version, missing out on half the bits. If you want all the bits to work, install the 64-bit version, like any sane person would.

The law does not work this way. You can't just suspend law enforcement because too many things that depend on breaking the law would stop working. The lawful answer is always to do the right thing, and if you have to stop billions of dollars' worth of illegal activity, well, tough. I am not, of course, arguing that this is a good thing for civilization, but "too big to fail" must never be allowed as an excuse for criminal activity.

> this device was quite much copied from Nokia's symbian phones

Even though we have remote controls today, and clicking on the article link no longer requires you to get your ass out of your chair, you can still make a fool of yourself by being too lazy to read it and discover that the first remote control was invented in 1955, long before there was Symbian, or mobile phones.

Although 64 bit programs also have to load libraries, those are shared among all the other programs. Since your 32 bit program is alone, all its libraries are not shared. xterm, for example, loads 6M worth of libraries, all of which will be shared with any other X application. Only 1.6M is used for runtime data. If you were to compile a 32 bit xterm and run it on the same machine, it will load an additional 6M of 32 bit libraries, increasing the amount of unshareable memory from 1.6M to 6M+1.6M, a fivefold increase.

Now all we need is for someone to use Emacsy to implement vi. That would be totally mindblowing!

The same thing that will happen to Windows 8.

Actually, the main problem with web pages is the current fad of using div background images as ui elements. "Use my colors" in Firefox turns off all backgrounds, and while that is indeed what I want, the UIs break. The correct solution, of course, is to use the img tag for images that are part of page content. Displaying backgrounds is supposed to be optional and any web designer relying on them for displaying content is doing it wrong.

There are a lot of people in the world who have sensitive eyes. A lot more than the blind. And still there is a lot of software that uses the black-text-on-white-background color scheme. Of all the possible choices, this is the one that causes the worst eyestrain. So if you are a software developer, take pity on hurting and watering eyes and allow us to use a darker color scheme. Windows Aero, I'm (not) looking at you!

When you talk about space savings due to use of 32 bit pointers, you forget that a 32 bit program running on a 64 bit system will need to load all 32 bit libraries, the size of which greatly exceeds the amount of whatever savings you may or may not achieve. I'd say that most programs don't need to be 32 bit, and should only be compiled for 32 bit only if there is a substantial measurable performance gain. Otherwise, it's nothing but premature optimization, which usually does more harm than good.