That is exactly why I won't even bother with this processor. If I have the source and it doesn't work with 64 I can compile it as 32 ok great. Now if I buy a game or something that I do not have the source for and it doesn't work what then? Companies will continue to distribute 32Bit applications, because they can support the most amount of platforms that way. As a result the 64 bit processor will just sit there doing 32bit operations.
The train is a beast, but the desitinations are limited
Exactly that attitude is what the FSF had to have had when they decided to write this "patch" Let the Stone throwing begin. Everyone knows SCO is full of shit why cripple GCC's support for SCO's Unix just because it can be done? Is this going to become a standard practice you done did us wrong now its your turn?
Slashdot Mirror
That is exactly why I won't even bother with this processor. If I have the source and it doesn't work with 64 I can compile it as 32 ok great. Now if I buy a game or something that I do not have the source for and it doesn't work what then? Companies will continue to distribute 32Bit applications, because they can support the most amount of platforms that way. As a result the 64 bit processor will just sit there doing 32bit operations.
:)
The train is a beast, but the desitinations are limited
Great
Exactly that attitude is what the FSF had to have had when they decided to write this "patch" Let the Stone throwing begin. Everyone knows SCO is full of shit why cripple GCC's support for SCO's Unix just because it can be done? Is this going to become a standard practice you done did us wrong now its your turn?