Sorry Google; you can Keep it to yourself
111–120 of 242 posts
Re: Sorry Google; you can Keep it to yourself
#112Re: Sorry Google; you can Keep it to yourself
#113Earlier quoted context omitted.
They're not dropping CalDav, they're just going to start screening its access: https://docs.google.com/forms/d/19gOLSlkTzHi-zub3BkMv7Ot0JML...
So how does that help me if I want to sync iCal with Google Calendar? Addendum: The way I read that form, they will only consider whitelisting apps if the developers ask for it. As a user, I'm still screwed.
Re: Sorry Google; you can Keep it to yourself
#114Earlier quoted context omitted.
Seems practically a given that Apple iCal and iOS will be whitelisted by Google as clients. Even Windows Phone 8 has that confirmed: http://www.engadget.com/2013/03/15/google-caldav-support-sti...
Actually, if you'll read the ZNet article that post is based on you'll notice that users who didn't connect their Windows Phone calendars to their Google accounts before February are still screwed! See also http://windows.microsoft.com/en-US//windows-8/use-google-win... : I want to connect my Google account after January 30, 2013 Here's what you need to know: Unfortunately, with Google changing the way it supports EA…
Re: Sorry Google; you can Keep it to yourself
#115At some point, when you have a ton of resources and people are shipping products out the wazoo.....you have to kill products. When you kill products, you lose confidence for future product announcements and skew your engagement numbers.
What is a company like Google to do, when their larger products command most of their resources?
Re: Sorry Google; you can Keep it to yourself
#116Earlier quoted context omitted.
>> I may just have forgotten them, though (2005 was a long time ago). Yeah, good point :-) There was Bloglines. It is still there, only difference being - it's a ghost town now. There used to be FeedDemon's own sync and now FeedDemon is jumping into the pyre with Reader. It's been long and I am out of example. Maybe others will bring some. But thing in this way - " because when the company launched Google Reader in 2…
The same could be said when they started Google - at the time Altavista was dominant in search. If you're that easily dissuaded, you shouldn't be in startups. There's almost always an existing solution to the problem you're trying to solve.
Re: Sorry Google; you can Keep it to yourself
#117I don't normally comment much, and when I do I try not to be negative. One thing I discovered in the last few days is that I have absolutely no patience for whining, especially when coming from grown man. This post, and a lot of comments around here sound like whining to me. These are my feelings regarding the recent Google Reader news and the comments surrounding it..
I want to be clear, I know why people are pissed off, some are angry because their beloved product was taken away, and for some, their trust was broken, perhaps more than once. It has certainly struck a nerve, and I want to have these conversations, but something about the tone of the people has really turned me off.
Re: Sorry Google; you can Keep it to yourself
#118Earlier quoted context omitted.
Seems practically a given that Apple iCal and iOS will be whitelisted by Google as clients. Even Windows Phone 8 has that confirmed: http://www.engadget.com/2013/03/15/google-caldav-support-sti...
To me it's not a given since AFAICT Apple software doesn't sync with Google Calendar over CalDav by default. Particularly on iOS you have to go out of your way to enable it—viz. you have to select 'Exchange account' instead of 'Google account'. In any case, if they're committed to preserving this feature then why are they implementing screening?
Seems unlikely they'll drop it given their approach to iOS so far has been to infiltrate the ecosystem with their own Google apps, though never say never I suppose.
As for why they're pushing people towards their own Calendar API, presumably so they can add/promote new features specific to Calendar which aren't present in CalDav. They can get more usage of Calendar-specific APIS/Features by pushing devs towards their own version, instead of letting them default to the CalDav API because that's what they're familiar with.
The responses gathered from API request form also act as a feedback mechanism for their own Calendar API, which they can use to fix any deficiencies.
Re: Sorry Google; you can Keep it to yourself
#119Evernote isn't exactly an angel. They butchered Skitch into a buggy piece of software that barely works.
Re: Sorry Google; you can Keep it to yourself
#120My favorite comment from the post: "And by the way – how is this app strategic for you guys and Reader is not? A little clarity would certainly be appreciated." I too would love to know what Google is thinking here.
I was finally connected with a developer evangelist, and I sent an email saying something like "would love to know more about Google's strategic goals with Hangouts".
Her response was "I'm sure you're aware that Google doesn't discuss its strategies outside the company".
What a striking cultural difference from startups, where we're constantly discussing our strategies together.