Linked by Thom Holwerda on Fri 1st Feb 2013 18:25 UTC
Windows A few days ago, Microsoft released the long-awaited Windows Phone 7.8 update for all those users who will be stuck on Windows Phone 7 forever because there's no upgrade path to Windows Phone 8 other than buying a new phone. Now that it's here, what, exactly, does WP7.8 to the table?
Permalink for comment 551205
To read all comments associated with this story, please click here.
tanzam75
Member since:
2011-05-19

The reason that Microsoft has so many XAML stacks is simple. Each division wants its own XAML stack. Remember that Microsoft's divisions are practically independent companies.

So that's why Microsoft ended up with three versions of XAML. (1) The DevDiv version, called WPF. (2) The Windows 8 version, called WinRT. (3) The Windows Phone 8 version, which is not-exactly-WinRT.

Plus, you have two deprecated XAMLs. (4) The second DevDiv version, called Silverlight. (5) The Windows Phone 7 version, based on Silverlight.

--

This isn't even scratching the surface. Microsoft has *four* Ribbons, *two* Visual C++ runtime libraries, *three* online storage solutions, *two* email/calendar servers, and *three* instant-messaging products.

In most cases, it's because the products live in different divisions. Basically, each division within Microsoft wants to be its own Microsoft.

Reply Parent Score: 9