Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Google Cloud Shell

cloud.google.com

Post reply on HN
Print view View original

161–162 of 162 posts

Re: Google Cloud Shell

#161

Post by TheIronYuppie »

TheIronYuppie wrote: post #15
rexignis wrote: post #11

Earlier quoted context omitted.

I wasn't explicit with my earlier comment, you're right about the beta period. I was referring to after when they exit beta and are a good, useful service for a year or two.

Disclosure: I work for Google. To the best of my recollection, I don't believe we've ever shutdown a product. Was there one in particular that hit you? (Reader, Wave, etc are totally different divisions.)

Crap. I literally meant to say "Google Cloud" and didn't. Yes, I'm well aware other products were shut down, but Google Cloud has not.

Re: Google Cloud Shell

#162

Post by jrochkind1 »

toyg wrote: post #59
KirinDave wrote: post #50

Earlier quoted context omitted.

It is not really Google's fault that Code was not a successful product, other than that they simply didn't have the energy/budget/will to actually make it a competitive product with Github.

Saying Google "doesn't have the budget" to do something is fairly preposterous, tbh. I can understand that they were wrong-footed by the rise of Github; Code was built to compete with Sourceforge, when GH didn't even exist. From day 1 though, it was clear that Code wasn't even "better enough" to actually kill SF for good; further development was incredibly slow. When Github hit their stride, Google reacted by just gi…

I think there was no reason for them to keep Google Code as a going concern with the rise of Github. They were not going to do as good a job as Github, and it wasn't something they were making any money off of.

Even if they had been trying.

But yes, like many Google products, it was basically released and abandoned. They weren't trying. (If they had been, maybe we never would have had a github...)

I do think as a public service, they could have left all the code (and wiki documentation) accessible read-only virtually perpetually. Surely they can afford that.

Instead, we get tarball download only, and only until late 2016, after which it's all gone forever, if it hasn't been migrated elsewhere by code owners or third parties.

Post reply on HN