Slashdot Mirror
Google Nixes Some Calendar Features and Other Software Offerings
An anonymous reader writes "Google on Friday announced it is shutting down a slew of features and services as part of its winter cleaning. Google Calendar will be losing a few features, Google Sync will be axed (on the consumer side), as will Google Calendar Sync, SyncML, the Issue Tracker Data API, and the Punchd app."
I hate it
iOS and android, I hate both versions
Might use yahoo again
Whether they are better yet, I'm not sure, but Yes, they have indicated that they want people using CardDAV/CalDav instead of Exchange.
Not too surprising, given that they have to pay MS for Exchange licensing, but I don't think these open protocols have the push support that Exchange had.
On other news sites, I read that Google today announces 18 new features. http://googleblog.blogspot.ca/2012/12/google-communities-and-photos.html etc.
And here: http://techcrunch.com/2012/12/14/google-gives-google-end-of-year-update-adds-low-bandwidth-hangouts-full-size-mobile-photo-backups-better-event-planning-animated-gifs-and-more/?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+Techcrunch+(TechCrunch)&source=email_rt_mc_body&ifp=0
Just Google it...
But on Slashdot, I read that drivel coming right out of Burston-Marsteller, or some other PR drone.
This is supposed to be a technology forum but somehow, some Slashdot editors perhaps seem to think that this is 'provoking' material, in the good sense of being humorous and driving up the number of comments?
But at what price? At what price, just in terms of credibility, for a beginning?
Could someone answer that?
Not unless you're using Exchange to do it:
Google Sync was designed to allow access to Gmail, Google Calendar, and Contacts via the Microsoft® Exchange ActiveSync® protocol. With the recent launch of CardDAV, Google now offers similar access via IMAP, CalDAV, and CardDAV, making it possible to build a seamless sync experience using open protocols.
GoogleSync and GoogleCalendarSync are Google's implementation of ActiveSync; they're not used to describe the general syncing features Google offers. This announcement is basically saying they're retiring a proprietary protocol in favour of open standards.
Just because you're paranoid doesn't mean there isn't an invisible demon about to eat your face
The summary was pretty terribly worded -- it didn't get across the fact that, essentially, this is stuff you're horridly unlikely to be using. The actual article was much clearer and more matter-of-fact about it.
That's because the summary wasn't designed to inform, it was designed to enrage. This is what passes for journalism these days.
Just because you're paranoid doesn't mean there isn't an invisible demon about to eat your face
Well, you're ignorant enough not to know what CalDAV is, yet still consider yourself knowledgeable enough to comment on the field, so I'd say that you're the natural target audience for trollish, flamebait headlines.
http://en.wikipedia.org/wiki/CalDAV#Implementations
http://en.wikipedia.org/wiki/CardDAV#Implementations
http://www.microsoft.com/about/legal/en/us/IntellectualProperty/IPLicensing/Programs/ExchangeActiveSyncProtocol.aspx
Also note that ActiveSync requires an MS license to implement. Now that's lock-in.
Just because you're paranoid doesn't mean there isn't an invisible demon about to eat your face
Seems like every time I sign up for a Google service and get used to it, within a couple years they pull the rug out from under me.
Apple is the same way - which is why I'm not relying on any of their services too heavily.
iTools became .Mac, which became MobileMe, which spawned iWork.com which shut down when MobileMe went away with the launch of iCloud.
Say what you want about Microsoft's shoddy products, at least they're consistent.
"Here is this new initative called Plays For Sure! "
*introduces the Zune*
"Plays for Sure is not supported on the Microsoft Zune®"
So they are essentially forcing me to use two applications for my email then, if I want push from them (since they are far from the only email provider I use).
Same shit different pile ;). All said, it's a move I've been intending for awhile anyway, so this is just motivation to make the move away from their services.
I was using the new Google Maps app for iOS the other day and it seems like every page i open it wants me to sign into my Google account so they can track me. Deleted. I prefer paid offline maps anyway, since I live in Canada and often travel where cell coverage is limited.
Welcome to the sweet world of Cloud. Where everything is cheap and available. Until it is not..
Lesson learned: If your business depends on specific tools or functionality, set up your own infrastructure.
To Terminate, or not to Terminate, that's the question - SCSIROB
There is an open standard for push support for email - IMAP IDLE. GMail implements it, as do most IMAP services, and a lot of IMAP clients. Microsoft's patented ActiveSync, designed for use with exchange/outlook, is also licenced by google both for client devices (android) and their servers, i.e. GMail/google apps, primarily so they can both connect to exchange as client, or serve up activesync for outlook clients. The server side is is now going away on their free personal gmail accounts - presumably because of the licencing fees for a not-often used service on their free version, as outlook also now supports IMAP IDLE.
Apple supports IMAP IDLE on OSX in Mail, but not iOS. It does support ActiveSync, so iOS can connect to Exchange servers. But Apple not supporting IMAP IDLE is the exception, not the rule. They say it's too power hungry for mobile devices, which is partly true - but activesync works very similarly, and is a similar power drain, and they support that.
Apple use their own method for iCloud I believe (which is why it fell foul of patent infringement in Germany, and had to turn off iCloud push support there).
So you have various options. Use the Gmail app, and get push that way (I don't know what method google uses for the App). Forward your google mail to icloud, and use that, if you want to hang onto your gmail address. Use a 3rd party app to implement IMAP IDLE support (for example PushMail on the app store should do it, it's aimed at Sparrow but does support the native Mail app on iOS by the looks of it). Implementing a 3rd party solution on iOS is tricky, as you need it to run in the background since iOS doesn't include IDLE support natively, and that is restricted heavily on iOS, which is why I believe Sparrow never got IDLE support.
But google was one of the very few services to implement activesync in the first place, apart from Exchange itself of course. If you want push email support, the standard is IMAP IDLE basically everywhere. So your complaint is that Google is dropping a patented, proprietary de-facto Microsoft standard for free accounts while keeping the open standard that Apple doesn't support on iOS, is to complain how evil Google is, and migrate to...?
A closed proprietary standard by Apple that only works with their software - iCloud? (Let's hope they keep that one going longer than mobile.me or its predecessors)
Another IMAP provider that provides IMAP IDLE support, but not Microsoft's activesync, leaving you in the same boat?
A hosted Exchange account? (shudder)
I'd suggest your actual problem is an insistence on using a client OS device that doesn't support open standards, and makes it very hard for 3rd party apps to do so.
Remember kids, it's all fun and games until someone commits wholesale galactic genocide.