Navigation

Search

Categories

On this page

Archive

Blogroll

Disclaimer
The opinions expressed herein are my own personal opinions and do not represent my employer's view in anyway.

RSS 2.0 | Atom 1.0 | CDF

Send mail to the author(s) E-mail

Total Posts: 81
This Year: 1
This Month: 0
This Week: 0
Comments: 33

Sign In
Pick a theme:

 Wednesday, September 14, 2011
Wednesday, September 14, 2011 2:07:41 PM (Eastern Standard Time, UTC-05:00) (  |  |  |  )

There are two different Windows 8 types: the tablet one, with ARM CPU, and desktop/laptop/server one, with Intel x86/x64/i386 CPUs. Old code base won't run on the ARM tablets, and Metro will not run on Windows 7,Vista and XP. Given that porting applications to Windows 8 is likely to be not trivial, here's the dilemma we, developers, face:

  • If we write WinRT/Metro UI applications, we'll be able to run it only on Windows 8, both ARM and Intel, but not on ealier Windows version. We'll also be able to sell it at Microsoft app store.
  • If we write a traditional Windows application, we will be able to run it on any non-ARM Windows version, including 8, losing ARM/tablet market and the ability to distribute the app via the app store.

So it all comes down to whether developers will believe that getting Metro/Tablet market is going to be worth forsaking Windows 7/Vista/XP desltop/laptop/server market.

Only Intel and AMD can truly save MS back by enabling legacy software on the tablet - if they create low-power yet fast, tablet-worthy x86 CPUs. This would enable programmers like me to write bulk of the logic in the backward-compatible modules and supply dual UI: Metro and traditional Win32. In other words, I'll do Metro programming sooner if Metro port is inexpensive, and if I don't lose backward compatibility with the huge install base of legacy Windows.

All comments require the approval of the site owner before being displayed.
Name
E-mail
(will show your gravatar icon)
Home page

Comment (HTML not allowed)  

Enter the code shown (prevents robots):