Dominik D
Regular
There's really no point in having ARM in console as something that would unify Windows platform. First of all: I don't believe OS codebase will be shared between desktop and console. There are tons of reasons*. Second of all: code portability has to do a lot with API portability and tools maturity. My Win32/C code works perfectly fine on x86, amd64 and IA64 - three very different beasts. And I'm not even thinking that much about making it portable: I just follow some guidelines, don't bind my code to, say, pointer size, endianness, etc. and I'm fine 99% of the time.I'm not saying that Arm will definitely be in the console, but there are some advantages and so it is a possibility for very little cost.
* the core concept of Windows is multitasking; the core concept of console is "run this game securely at max perf". This difference makes it hard to have generic OS components that can be shared: your I/O has to be secure on the console, so your I/O stack is different; you have no paging, so your memory manager has to be different; your OS tasks have strict budget so your background services have to work differently; your HW cannot be compromised so you run on top of a super-tight hypervisor; your graphics API does not need all the abstraction layers you need on PC, so you strip WDDM completely; and so on... I mean - it'd be cool to have one code base, but I don't think it's gonna happen for X3.