Linked by Thom Holwerda on Mon 21st Jan 2013 21:17 UTC
Windows The Verge has a learned a few interesting things about Google deprecating EAS and how this will affect Windows Phone users. As it turns out, Google informed Microsoft it was planning to remove EAS in the summer of last year, but without giving a firm date. Microsoft has been trying to get a six-month extension from Google, but so far with no luck. In the meantime, Microsoft is also working on adding CardDAV and CalDAV support to Windows Phone - so yay open standards.
Permalink for comment 549803
To read all comments associated with this story, please click here.
lemur2
Member since:
2007-02-17

I'm unsure, but it is part of my issue with this hatchet they're taking to EAS. Without a suitable solution in place, it is irresponsible to reduce consumer functionality. I wish Google was a little more pragmatic.


EAS is proprietary, from an end-user point of view it results in lock-in to a single supplier, and introduces requirement for the consumer to have to pay royalties. To retain such a standard as the only means of access is to reduce consumer functionality. To get rid of such a lock-in to a proprietary pay-per-access "standard" is by far the best thing to happen, from a consumer perspective.

I put the word "standard" in italics here, in relation to EAS, because a true standard is mean to enable inter-operability of different products. See here for a definition:
http://en.wikipedia.org/wiki/Software_standard
"A software standard is a standard, protocol, or other common format of a document, file, or data transfer accepted and used by one or more software developers while working on one or more than one computer programs. Software standards enable interoperability between different programs created by different developers."

EAS constrains consumers to MS products only. If anything, it is an anti-standard.

This is a self-evident truth. How could you have possibly got it so backwards?

Reply Parent Score: 5