Linked by Thom Holwerda on Thu 27th Dec 2012 19:50 UTC
Thread beginning with comment 546550
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
Linked by Thom Holwerda on 05/16/13 21:41 UTC
Linked by Thom Holwerda on 05/16/13 17:04 UTC
More News »
Sponsored Links



Member since:
2005-11-29
The Windows Phone team is one of many within Microsoft. Even with a Company the size of Microsoft's, there are still time constraints on engineering resources.
Think about all that the Windows Phone had to develop in-house prior to Windows Phone 8:
- Their own fork of the CE Kernel (hybrid CE6 and CE7)
- Their own fork of the .NET CF (3.7 vs 3.5 on CE6/7)
- Their own mobile XAML Stack
- Their own telephony and data stacks
- Their cloud infrastructure for Zune and the Application Store.
Now with the unification of Windows 8 and Windows Phone 8 a lot of that work is offloaded to the Windows team (Kernel, Cloud Services, .NET CoreCLR, Telephony+3G/4G stacks, and in the future hopefully XAML), so hopefully moving forward some of that engineering talent is freed up to work on other issues.
This internal alignment within Microsoft will take multiple product cycles likely, but in the end should represent an organization that is a lot more nimble.
It still is a testament to the Windows Phone team that they managed so much internally for so long.