viability of 64-bit systems

http://www.diablofans.com/forums/showpost.php?p=483100&postcount=19
It has absolutely nothing to do with being (un)stable.
Have you already forgotten how it took them longer to get Flash on 64-bit platform than what it's taken Blizzard to develop D3? It wasn't the first and sure won't be the last "minor issue", and if something as trivial as that isn't supported at all, the sharpest among us could draw some conclusions. I'll check back in a couple of years, but everyone buying a 64-bit system for home use is just wasting money based on insufficient brain activity.
I'm not even gonna bother with the "runs stuff" argument. In case you weren't aware, operation systems also have other problems than just freeze-crashes where you lose all control.

TRUE OR FALSE?

Discuss.

>>4
Using inline Assembly will make the program hard to port to any architecture, not just x86-64. That's a risk you take when you choose to use Assembly. As for parts in pure C, if you did something stupid like depending on long being 32 bits long, or assuming little endianness, then the code is not well-written.
If your code is filled with shit like that and you didn't comment the unportable parts, then yes, porting to other platforms may take as long as a full rewrite.

The whole point of C is that it's portable.