> I bet they switch back to x86 then. Watch them go Athlon64.
I dunno why they didn't in the first place... That would've made a lot more sense than going with the PowerPC in my opinion, especially in regards to porting games to work on Windows XP, unless MS has something up their sleeve.
Maybe MS expects everyone to program on the .NET platform and not target the PowerPC directly. For the X-Box, MS forbade anyone to access the hardware directly and the SDK only let them work with the APIs that MS provided them. This is what MS would like people to do anyway on the PC! So perhaps MS is making developers build .NET code on the X-Box 2, and that will be the standard SDK. They have no reason not to.
When everyone is on .NET, and they bring their games over to Windows (or they do it the other way around, in that case doing it in .NET on PC would be beneficial as well), then that will automatically create a huge pool of .NET software, development tools, graphics tools (don't forget that the X-Box 2 SDK is just a G5 with Windows NT right now).
If the X-Box 2 is the dominant gaming platform in the next round of console wars, MS will be able to use that to leverage what happens on the PC. For example, if you make a popular game, it will be for the X-Box 2, just the way the PSX and PS2 enjoyed the most popular titles because it was the most popular system. So a lot more people are on that platform because it means they will get higher selling games. Suddenly .NET is the most supported platform because everyone uses it, and that will automatically spill over onto PC because .NET will run the same code on both platforms.
Perhaps the X-Box 2/PC is just hinting at what's to come, closed-box 100% .NET Microsoft boxes, and MS are the only providers of a .NET SDK, so like consoles, they will be able to choose who gets them? That's reaching kinda far, but I don't exactly know how far MS wants to go, or how far they can go legally. But if you can make a closed console, there's nothing saying you can't make a closed PC. Is there?