Microsoft, Google kiss and make up over EAS for Windows Phone
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).
E-mail Print r 1   19 Comment(s) http://osne.ws/kn0
Thread beginning with comment 550991
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: But but�
by Nelson on Thu 31st Jan 2013 05:24 UTC in reply to "But but…"
Nelson
Member since:
2005-11-29

It is part incompetence, part time/engineering constraints.

Thing are better with WP8 when it comes to sharing between the platforms, but its in the midst of a transition rather than at the end of one.

As a dev, I can tell you that it needs to happen faster and its annoying considering the potential.

Reply Parent Score: 4

bentoo Member since:
2012-09-21

It is part incompetence, part time/engineering constraints.


Just like Google's incompetence for not supporting CalDAV and CardDAV in Android right?

Edited 2013-01-31 15:12 UTC

Reply Parent Score: 1

sgtrock Member since:
2011-05-13

...if you start with the known assumption that you're going to be supporting more than one hardware platform. For example, Linux and the BSDs all support a HUGE range of hardware platforms. The amount of architecture specific code is less than 5% in those cases.

Yet Microsoft seems to have failed to do so in this instance for no really good reason. What is mind boggling to me is just how badly Microsoft seems to be at it these days, given how good they used to be at it. Anyone else fondly remember the early versions of NT on the DEC Alpha chipset? :-)

Reply Parent Score: 2

lucas_maximus Member since:
2009-08-18

The problem is not necessarily the code itself, it the QA and test devices. I know I been in situations where I haven't supported X and Y because there just wasn't time and it had to be de-scoped.

Reply Parent Score: 3

Nelson Member since:
2005-11-29

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