The importance of x86 is overstated too. Many applications will be pretty close to a recompile away. There is of course the usual chicken-and-egg issue that all platforms have, but if Windows/ARM (WARM?) takes off, they will be recompiled.
The importance of x86 is overstated too. Many applications will be pretty close to a recompile away. There is of course the usual chicken-and-egg issue that all platforms have, but if Windows/ARM (WARM?) takes off, they will be recompiled.
And if there is vendor support, then they would probably just get something certified for the ARM systems.
EDIT: The flamewar detector is preventing me from replying, but I don't think anybody is really disagreeing all that much.
I agree with Ken, most of the business applications in big corporations are based on .NET. (J2EE used to be big but from what I am seeing .NET is eating J2EE's lunch)
The only thing I am saying is that even if the bytecode theoretically makes it possible, businesses will not generally want to move their applications to a new operating system and platform without the involved vendors supporting it. Hence, .NET vs native is not all that important, because they would just get new versions from the involved vendors anyway.
I agree with Ken, most of the business applications in big corporations are based on .NET. (J2EE used to be big but from what I am seeing .NET is eating J2EE's lunch)
For example, a company may have a matching donations program, and they may have a LOB app that employees go to to submit requests for matching funds, see status, list of qualifying charities, etc...
Large enterprises are often filled with hundreds, if not thousands of these applications. These applications are often what dictate the platform a company uses.