Hacker News Reader

Comment by donw | Hacker News Reader

I wonder how many users will come to depend on it before they shut it down.

I give it 2 years. Maybe only 18 months. I don't even know how many different (and confusing!) chat applications Google has launched already. Seems like their engineers, when they get bored, write a chat app.

Next time I see someone mention how great their monolithic repository is I'll ask how many chat applications you have to checkout before you can code at google.

There was an article posted on here a few months ago about Google's version control system. One of the main features is that you don't actually checkout copies of every file in the repository; instead they're faulted in as you need them.

My impression is that the monolithic repository only works because Google's built a bunch of custom tooling to support it. It doesn't mean any company can just roll all of their code into a single Git repository and call it a day.

This maybe? http://m.cacm.acm.org/magazines/2016/7/204032-why-google-sto...

The key here is CITC. All the source code lives "in the cloud" and pulls to your machine as it's needed (using a FUSE file system).

Yes, that's it, and that's the key feature I was talking about.

Google reader will always be missed.

They should code name the next one "stillborn".

New Google Ecosystems: Not even once.

This is overblown, the biggest thing they did this to was Reader, and that was hardly an "ecosystem" app without any way to use a stand-in replacement within minutes.

You do realize reader had comment sections, likes, etc?

It was a full-blown social network for a while.

Reply on news.ycombinator.com