Linked by Thom Holwerda on Wed 30th Jan 2013 23:14 UTC
Windows So, just as Windows Phone 7.8 has finally started rolling out to devices, Microsoft and Google kiss and make up about the whole dropping of EAS thing. Google has extended its EAS support for Windows Phone users for six months, and Microsoft will add CardDAV and CalDAV support to Windows Phone (but not Windows 8/RT, so those users are still screwed by Microsoft's incompetence).
Permalink for comment 551049
To read all comments associated with this story, please click here.
Member since:

What specifically are you talking about? The differences in XAML?

They are results of being caught in different release cycles.

Windows Phone uses the Silverlight Runtime. Windows 8 uses its successor.

During the WP8 timeline there was not enough time to backport the Windows 8 XAML engine.

It is incompetence from a resource budgeting POV (they prioritized other things above it), but I don't think it speaks of a lack of portability.

Silverlight is notoriously portable. Windows Phone 8 uses the same Windows Kernel, and even the same Windows Runtime a Windows 8. The only difference is the XAML stacks.

Even the .NET engine moved from .NET CF 3.7 to CoreCLR 4.5 to match Windows 8. That was a huge technical feat, especially since they maintained compat with WP7 apps.

Edited 2013-01-31 17:41 UTC

Reply Parent Score: 3