Linked by Thom Holwerda on Fri 1st Feb 2013 18:25 UTC
Permalink for comment 551205
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/25/13 0:45 UTC
Linked by Thom Holwerda on 05/24/13 23:59 UTC
Linked by Thom Holwerda on 05/24/13 22:33 UTC
Linked by Howard Fosdick on 05/24/13 21:41 UTC
Linked by Thom Holwerda on 05/24/13 14:44 UTC
Linked by Thom Holwerda on 05/23/13 23:22 UTC
Linked by Thom Holwerda on 05/23/13 22:04 UTC
Linked by Thom Holwerda on 05/23/13 22:01 UTC
Linked by Thom Holwerda on 05/23/13 17:52 UTC
Linked by Thom Holwerda on 05/22/13 22:23 UTC
More News »
Sponsored Links



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.