I know I'll get modded down for this, but saying "Yeah, I know you'll mod me down for this," pretty much guarantees you'll get modded up.

No one cared about GTA 3 at launch. It was only a couple months later after they had played it at their friend's house that people started buying a lot of copies of it. And then they launched the sequel and people did care about that. Look at this chart.

See also the Unladen swallow project, which is using LLVM to speed up Python. They're still in the very early stages, but it looks promising.

You see, it's thoroughly reasoned out reactions like yours that make me wonder why people are constantly crying about racism. Clearly, there are no more idiotic racist fucks on the internet, so there must not be any in real life either.

btw, you know what was the comment of my gf, when I said that I would like to have a phone with a full qwerty-keyboard, complaining that, at that time, no phone was available?

The Japanese I know prefer cellphone-style input for Japanese to qwerty. The Japanese alphabet just so happens to split up logically into ten groups, so it makes a lot of sense to use a number pad to type them. Combined with predictive text, it's pretty quick. On the other hand, the layout of the qwerty keyboard is basically random. So, the Japanese aren't really interested in using micro keyboards when a number pad works well enough and doesn't hurt your thumbs.

Yes, but the Japanese web is mostly designed for use with crappy cellphone browsers, so it already sucks. Because their phone company charged by the minute, no one used dial up internet back in the day, but their cellphones were really good, so everyone used cellphones. So, their web has always had the assumption that your browser sucks built in.

In fairness though, isn't Atari a special case? They were developing what they thought of as unimportant children's toys (did we lose the spec to the original Hula Hoop too? Oh noes!) and then they went bankrupt several times. The current holder of the name "Atari" and attendant IP has absolutely zero connection to the original Atari.

That said, copyrights that are longer than 20 years are insane.

Sorry Al, God throws dice all the time...

Not necessarily. The Bell experiments show that either God plays dice or God acts non-locally. The Bohmian interpretation, for example, hasn't yet been conclusively disproven, and it's deterministic.

The G3 iPod? The ugly ass one with the red buttons that all felt the same and gave no physical response? That one was not missed. The click-wheel was a stroke of genius.

Tables, divs, whatever, but please at least do this when you use tables:

<table class="bare-layout-table"><tr>
<td class="sidebar"><% sidebar %></td>
<td class="content"><% content %></td>
</tr></table>

Do not clutter up your page with useless, meaningless extra divs.

Speed of light: 3 x 10^8 m/s
Reasonable chip size: 1cm
Ask uncle Google about "(300 000 000 (m / s)) / (1 cm)"

Response: 30 gigahertz

We will never see another 10x speed up on the basis of clockrate. Forget the heat thing (although that's also a killer), clockrate is dead, dead, dead.

Gee, thanks for assuming that I'm incompetent. No, I use an actual text editor (which even shows you the different between spaces and tabs and everything), not Notepad. Step one was the hardest because I assumed that I needed to replace the tabs with 4 spaces, like God intended, but when I ran it, I saw that it didn't work, and quickly realized that it was meant to be replaced with 8 spaces. All of the other steps worked the first time, which made step one the hardest relatively speaking, but none of the steps (including one) was especially hard. Maybe if I used a crappy text editor that doesn't distinguish tabs and spaces number one would have been actually hard, but if you program in Python without being aware of the difference between tabs and spaces the fault is your own.

You misspelled puts? ;-D

Here's code you can put in your Python 2.x code today to future proof it against the change to xrange:

try:
      range = xrange
except NameError:
      pass

After that, just write range in your code and it will automatically use the equivalent of Python 2's xrange. If you're running Python 2.6, you can use a print function (instead of a print keyword) by adding from __future__ import print_function to your header as well, and you're good to go for a large number of Python 3 switching problems.

I got it to run in Python 3, and here are the changes I need to make:

1) The file was screwed up and used a tab instead of 8 spaces (a problem unrelated to Python 3).
2) I had to change all the print statements into print functions by wrapping the argument in parentheses.
3) I had to change xrange to range.
4) I had to add from functools import reduce to the top of the file.

Done. 4 changes made in 5 minutes, the hardest of which (#1) would have screwed up Python 2.x as well.