3 ms·
Google need to learn that providing a free service and then retracting it is quite damaging to their reputation. I know many developers who are incredibly reluc
by onion2k 10y ago
Google need to learn that providing a free service and then retracting it is quite damaging to their reputation. I know many developers who are incredibly reluctant to build on Google APIs because the danger of them being shut down feels high.
However, interest and use of the API has waned over time, and it is running on API infrastructure that is now two generations old at Google.
I wonder if there's a correlation between the downturn in interest in RSS and Google Reader being closed.
- TeMPOraL 10y ago> However, interest and use of the API has waned over time, and it is running on API infrastructure that is now two generations old at Google. That's funny. This is software, not nuclear reactor maintenance. It costs very little to let old software run, especially in case of a Google-sized company. If beancounters complain, then budget it as a marketing expense!
- solipsism 10y agoLittle to keep the API running indefinitely, but not the infrastructure.
- TeMPOraL 10y agoI meant both, actually. Keeping the API running == keeping its infrastructure running. And I can't imagine this costs them very much.
- solipsism 10y agoYou imagine wrong, it takes teams of people to keep running the infrastructure that Google is built on. And keeping running infrastructure that's multiple generations old is wasteful. What you should be arguing is that it's worth it for Google to port the API to current infrastructure. But porting it is not as simple as saying "Leave it up!"
- fixermark 10y ago> It costs very little to let old software run, especially in case of a Google-sized company. The cost model is actually the reverse of what you may think. Because of security concerns, every existing service is a vector for attack waiting to happen; under-maintained services doubly so, as they won't have the passive eyes-on that minimize the chances of something slipping through the cracks. At a company the size of Google, it's not just the passive cost of maintaining the API; it's the active cost of maintaining the API, maintaining the servers its implementation is running on, and doing the security concern analysis to make sure someone can't use the feeds API to crack into a user's GMail account, multiplied across all services Google runs, etc.
- spriggan3 10y ago> I wonder if there's a correlation between the downturn in interest in RSS and Google Reader being closed. Google Reader was a great app, I didn't believe Google one second when they basically said that nobody used it anymore. RSS is still the best way for me, personally, to get my news from the internet on a whole range of subjects. I don't like Twitter or Facebook which are mostly noise and spam. With RSS I get my news right from the source, without a third party. I also use RSS in APIs I write for pub-sub endpoints. Google could have integrated RSS in Gmail for instance,the same way they integrated a chat inside the email client. They didn't because they don't believe in open tech that much anymore. It's all about messaging apps with proprietary protocols these days. Yet RSS is part of the web.
- leephillips 10y agoAmen to the RSS love. It's either that or write a spider that scrapes the websites you want to follow, looking for changes.
- eru 10y agoReader user base wasn't really growing (in terms that Google is used to). But more importantly, the technology was creaking, and nobody at Google wanted to maintain it. (Disclaimer: I ended up working for the team that shut down Reader.)
- solipsism 10y ago3 years to figure out another option isn't enough time for your developer friends? It's not like they're just pulling the rug out from anyone without warning. They require a promise that the free service will be maintained for them forever?
- Klathmon 10y agoSeriously. This isn't Google shutting down something out of the blue, this is them shutting down the service 4 years after they announced it would be shut down in 3 years... Does everyone here really expect every company to keep every service running indefinitely?
- onion2k 10y agoDoes everyone here really expect every company to keep every service running indefinitely? No, but if a company wants developers to build things on top of those services (or any other service they offer) then they need to make sure it doesn't feel like they might close down a service on a whim. Take Facebook as a counter-example. Their APIs change with irritating frequency, but I've never heard of them shutting anything down. That's not to say they don't, but I'm not of the opinion that there's any danger to my business in building services that reply on Facebook's infrastructure. I can't the same of Google. I know Google shut things down, so I avoid building on Google APIs. To Google's credit the way that they sunset services is very good.
- realityking 10y agoWell, they did shut down Parse. And that was even a paid offering.
- mkozlows 10y agoThe correlation is backward. RSS usage had flatlined as Twitter/Facebook took over the use cases of RSS for most people; with RSS in decline, Reader was killed... and now, years later, so is this Feed API. Yes, you like RSS. So do I. But most people never used it. Feedly has 15 million users, and they estimated that they captured 85% of Google Reader's user base when it shut down. Twitter is 20x larger. Facebook is 100x larger.
- munificent 10y ago> Google need to learn that providing a free service and then retracting it is quite damaging to their reputation. Let's say someone invites you to a party for free, and offers chips and snacks. If, eventually, the snacks run out and the bowl is empty, should you be justified in being mad at them? You got free snacks, after all. You just didn't get an infinite supply of them. > I know many developers who are incredibly reluctant to build on Google APIs because the danger of them being shut down feels high. If you get invited to a party with free chips and snacks, and the host even says it's fine for you to take those snacks and sell them to other people, it seems the height of entitlement to me to get mad when the bowl runs out eventually. Sure, you might have to figure out how to adapt your business to a new post-free-snacks world, but you still got several years of free chips that you could then use in your own business before then. I'm having a hard time understanding how this makes Google look at all bad.