Linked by Thom Holwerda on Mon 21st Jan 2013 21:17 UTC
Thread beginning with comment 549827
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.
RE[8]: really - what's wrong with *DAV?
by JAlexoid on Tue 22nd Jan 2013 08:14
in reply to "RE[7]: really - what's wrong with *DAV?"
RE[9]: really - what's wrong with *DAV?
by Nelson on Tue 22nd Jan 2013 08:22
in reply to "RE[8]: really - what's wrong with *DAV?"
Well you can't live without your favourite stalker, can't you?
It's wrong morally, but the consumer has had no impact.
It's wrong morally, but the consumer has had no impact.
Hey, at least it is possible to have a sensible discussion with you. Hell, these days I'll take that.
And, in light of these new events (DAV support), I'd say the consumer impact is greatly diminished. If Microsoft implements IMAP IDLE (only push extension Gmail supports iirc) then it will be largely transparent to the user.
I wonder if Google will give Microsoft the extension they ask for, though.




Member since:
2005-11-29
Now please tell me how is the consumer impacted negatively here? (First look up the definition of consumer, vs customer)
Did the deprecation of EAS on free Google services make it impossible to use Outlook.com or other services that provide the same functionality?
I was wondering when you'd show up. No, not impossible, just inconvenient.
Everything can be worked around, but jut telling people to switch to Outlook.com is the wrong answer.
Google either needed to relent or Microsoft needed to implement DAV (which it looks like they're doing). Telling people to migrate all of their data over somewhere else over a political decision is stupid.