Windows IT Pro is the leading independent community for IT professionals deploying Microsoft Windows server and client applications and technologies.
  
  
  Advanced Search 


June 30, 2009

Where Have All the (Microsoft) Platforms Gone?

Developers are ignoring Microsoft and yes, you should care
RSS
Subscribe to Windows IT Pro | See More News and Analysis Articles Here | Reprints | Or get the Monthly Online Pass—only $5.95 a month!

Many people think of Microsoft as a software maker, but it’s more accurate to describe the company as a platforms maker. Windows, Windows Server, Office, Internet Explorer, Xbox, Windows Media, Zune, SharePoint, and many other Microsoft products are actually platforms that developers can build off of to create their own custom solutions.

Microsoft's success as a platforms maker is unsurpassed, but it seems that in recent years developers have been ignoring some of Microsoft's most innovative platform improvements. Why is this?

The most egregious example of this, perhaps, is the Windows Presentation Foundation (WPF, formerly "Avalon") technologies that Microsoft first provided with Windows Vista. Back in 2003, Microsoft treated Professional Developer Conference (PDC) attendees with a peek at the underpinnings of the Windows applications of the future. It was a heady time, and we were shown resolution-independent scaling, automated and complex text flow, and other special effects that would be the hallmark of the post-Win32, post-Microsoft Foundation Class (MFC) world.

It was not to be. Today's Windows applications look identical to those from almost a decade ago, the only material difference being that the window "ornamentation" has changed due to UI differences between Windows XP, Vista, and 7. Developers have only slowly embraced .NET, from what I can tell, let alone later .NET-based technologies like WPF.

Part of the problem, of course, was the public reaction to Windows Vista. Though the OS is actually as broadly deployed in businesses as was XP during the same time frame in its life cycle, Vista has the smell of death about it, and virtually everyone I've ever talked to has described it in negative terms, regardless of their lack of actual real world experience with the OS.

That's not completely it, of course. Microsoft back-ported most Vista-era platform technologies to Windows XP, perhaps understanding they would be a tough sell otherwise. That doesn't seem to have mattered, however. I can't think of a major WPF application. (And no, The New York Times Reader and several Twitter front-ends don't count.) Most damning, perhaps, even Microsoft has eschewed these leading-edge technologies in its own applications. You'd think the Windows Live Essentials applications and the bundled apps in Windows 7 would be WPF example applications. They're not.

Instead, in Windows 7, we get minor additions to the Windows platform. The ribbon UI that first appeared in Office 2007 gets a formal unveiling in Windows 7, and, sure enough, Microsoft even supplies two sample ribbon apps, WordPad and Paint, to inspire developers. But these basic apps aren't exactly inspiring, especially when you compare them to the WPF apps we first saw six years ago.

Of course, the world is moving on as well, and as more cloud computing solutions arrive, the platform of choice inevitably becomes the web. In that market, there is plenty of room for improvement, since the web is relatively immature compared to traditional PC platforms like Windows. But the barrier to entry is also lower: It's much easier to create and deploy a web application than a Windows application.

And that, ultimately, is the problem, from Microsoft's perspective. On the web, Microsoft is lagging behind efforts from competitors like Google, not to mention emerging web standards like HTML 5. The platform momentum, put simply, has moved away from Microsoft's traditional products and into markets Microsoft doesn’t dominate. In some cases, the company is barely a player.

Does this affect you? Indirectly, yes. Anyone who has made a big bet on Microsoft technologies has a vested interest in the company's continued success. Obviously, success can be measured in different ways. But if you accept that the adoption of its platforms is an important barometer of Microsoft's success, it seems that the company has at least temporarily stalled.

End of Article



Reader Comments
WPF is interesting, but is it really useful for business apps (e.g. inventory tracking, returns, etc)? As a developer, my users prefer their apps simple. Why bother with having a rotating button, or one that changes color?

scottm99999 July 01, 2009 (Article Rating: )


Times Reader isn't even based on Microsoft technology anymore. They switched to Adobe AIR with their current version.

jmetzner1 July 01, 2009 (Article Rating: )


WPF is astounding technology. It has tremendous use in a modern day UI. Winforms are often a static size using bitmaps for graphics. Displays are getting very large and Winforms don't grow well. They usually don't grow at all. WFP solves all of this is an amazing way. WFP is also a lighter technology than Winforms. Using XAML for vector based graphics is also astounding. We have developed an enormous application for law enforcement and its 100% WPF. It is the only way to go.

alp@lanproinc.com July 01, 2009 (Article Rating: )


There's nothing to stop you from creating "simple" apps in WPF. The fancy graphics and animations are all optional. The data-binding syntax takes some getting used to, but it's much simpler than the WinForms equivalent - particularly when you combine it with a ViewModel.

The main problem is that there is a lot of WinForms/MFC/ATL code out there, and nobody willing to pay to re-write it in WPF. Also, there is a steep learning curve; quite a few developers coming from WinForms try to write WPF code in the same way, fail, and conclude that "WPF Sux".

There are a few bugs and issues in WPF which need to be fixed - for example, the text rendering, which is allegedly fixed in v4. Otherwise, I don't see any benefit to starting new rich-client forms projects in anything else.

richard_d July 02, 2009 (Article Rating: )


You must be a registered user or online subscriber to comment on this article. Please log on before posting a comment. Are you a new visitor? Register now




Top Viewed ArticlesView all articles
WinInfo Short Takes: Week of November 9, 2009

An often irreverent look at some of the week's other news, including some more Windows 7 sales momentum, some Sophos stupidity, Microsoft's cloud computing self-loathing, more whining from the browser makers, Zoho's "Fake Office," and much, much more ...

Command Prompt Tricks

One reader shares his tip for setting up the command prompt to reflect a remote path. ...

Understanding File-Size Limits on NTFS and FAT

A general confusion about files sizes on FAT seems to stem from FAT32's file-size limit of 4GB and partition-size limit of 2TB. ...


Related Events WinConnections and Microsoft® Exchange Connections

DevConnections, Microsoft® ASP.NET Connections, SharePoint Connections and SQL Server Connections

Deep Dive into Windows Server 2008 R2 presented by John Savill

Check out our list of Free Email Newsletters!

News and Analysis eBooks Getting Maximum Performance from Your Web-based Applications

Business Process Automation - Managing Cost in Your Enterprise

Understanding and Leveraging Code Signing Technologies

Related News and Analysis Resources Introducing Left-Brain.com, the online IT bookstore
Looking for books, CDs, toolkits, eBooks? Prime your mind at Left-Brain.com

Discover Windows IT Pro eLearning Series!
Clear & detailed technical information and helpful how-to's, all in our trademark no-nonsense format


Windows IT Pro Home Register FAQ for Windows WinInfo News
Europe Edition About Us Contact Us/Customer Service Media Kit Affiliates / Licensing  
SQL Server Magazine Office & SharePoint Pro DevProConnections IT Job Hound
Left-Brain.com Technology Resource Directory asp.netPRO ITTV Windows SuperSite 
 
 Windows IT Pro is a Division of Penton Media Inc.
 © 2009 Penton Media, Inc. Terms of Use | Privacy Statement