Hacker News new | comments | show | ask | jobs | submit login

The way Google runs its services, much of the infrastructure is an existing back-end (yay, map reduce, also an inherent front-side CDN). There's some application-specific hosting, but it's a relatively thin layer. So the hosting costs aren't all that huge.

My read: the stated rationale for killing Google Reader, especially in light of the huge cry of protest and impacts on blog traffic (Rob Malda posted web traffic results showing huge declines at WordPress and other blog sites at WashPo) suggests to me something else at work.

Just a hunch.




> My read: the stated rationale for killing Google Reader, especially in light of the huge cry of protest and impacts on blog traffic (Rob Malda posted web traffic results showing huge declines at WordPress and other blog sites at WashPo) suggests to me something else at work.

Usual theory about driving "updates" traffic away from decentralized RSS and into proprietary arms of Google+. Twitter removed RSS feed access to an account's updates for the same reason.


I was being a bit too sarcastic perhaps. My point was that I hope that everyone who regularly visits this site knows that keeping any kind of webservice up and running takes time. No matter how automated it is.

But I completely agree that there is probably an alternate force at work here.




Applications are open for YC Winter 2018

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | DMCA | Apply to YC | Contact

Search: