3 ms·
You're right, but it wasn't about competing product... It was about competing cost. Specifically, competition for hardware resources and engineers. Social impo
by shadowgovt 6y ago
You're right, but it wasn't about competing product... It was about competing cost. Specifically, competition for hardware resources and engineers.
Social imposed upon Google substantial new costs under-the-hood in terms of infrastructure and time to implement. You wouldn't think a Facebook competitor would require a lot of compute and storage resources, or a lot of engineering hours, but Google had high hopes regarding what the platform would become, and they definitely didn't want to get blocked by lack of resources. In addition, a massive internal infrastructure overhaul to the accounts system that was coupled with the social initiative required a re-architecting of every app that had an "account" concept attached to it.
On the grand balance sheet, Reader was a product with a non-growing userbase, didn't align with Google's long-term strategy goals, took resources to maintain, consumed storage and compute resources that could be used for more valuable bets, and was on track for a software re-architecting (which faced Google with the alternative of saving the eng-hour cost by just killing it instead of re-architecting it). Those facets combined put it on the chopping block.