Despite developer complaints, this is the right thing to do. Technology changes, and Microsoft has to make this shift with everyone else. It’s better for the user, better for the business, and better for everyone involved in the long run.
From a business and technical perspective, this makes sense. Windows 8 will run on a bunch of different hardware — traditional Intel x86 chips, new Intel systems-on-a-chip, and at least four different flavors of ARM. Programming separately for each of these platforms is complicated — it would require developers to recompile their code for each platform, and perhaps rewrite portions that don’t work.
That not only makes their past experience less useful, but also opens development to an army of Web-focused developers who have never been particularly interested in Microsoft. Suddenly all these young hotshot Web jockeys will be able to write competitive Windows programs? That’s a lot to bear for the guy who spent a decade perfecting C#.
It could mean truly cross-platform applications (i.e. get rid of Flex). It’ll take a while to build tools that will catchup to Visual Studio. But in the meantime, more developers will be able to develop for the platform, and it’ll bring more (and possibly more usable) applications to Windows.
That’s a bad thing?
$99 Tough Love Resume and Portfolio Review
Tough love. Great Advice. Receive an one hour portfolio review and career coaching session online, or in person if you're in Seattle.
Other Posts On Usability Counts
- Six Reasons Why The Shortage Of UI Engineers Is Going To Get Worse
- Digital Trends: The Re-imagined Windows 8 Metro Concept That You Wish Was Real
- CMS Fridays: SharePoint And The Square Peg, Round Hole Scenario
- Cloud Computing: What Does It Mean For User Experience? A Lot. And It’s All Good.
- The Unicorn Designer Dilemma: How To Avoid It