So, what if you don't have that button? Is there a minimum amount of product you need to have before this service becomes active?
Google Cloud Shell
21–30 of 162 posts
Re: Google Cloud Shell
#22Earlier quoted context omitted.
I normally am quite reserved about language use, but comparing google to OVH? Seriously? OVH is a dysfunctional company that somehow turns a profit. We almost lost our company's domain name twice due to their incompetence.
Twice? Well....
Which is why we moved away from them of course...
Re: Google Cloud Shell
#23Earlier 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.)
Google Drive hosting, to be fair it still works and you guys gave plenty of heads up (August 31, 2016). Just because they are in different divisions doesn't mean Google hasn't shut things down.
Re: Google Cloud Shell
#24Albeit much different, yet with some common ideas, I've created a docker “devops environment” image, that if you provide with a GCE service account, it will auto-activate google cloud and even setup ansible to work with your gce project. Emacs and vim are provided, pre-configured to a certain degree. The best usage scenario would be emacs+golang but there is basic support for other languages. There are some other conveniences too, like bash-completion being enabled (no more need for remembering all git flags).
If anyone is interested or want to borrow some ideas:
Re: Google Cloud Shell
#25> Use of the Cloud Shell is free through the end of 2015: you will not be charged for any resource utilization. Would be nice if they could have stated how much it's going to cost later on. We're less than three months from 2016.
They likely don't know how this is going to be used, so they want to gather usage statistics (both user and resource) to determine what it should cost.
Re: Google Cloud Shell
#26Earlier 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.
Which would be understandable if they ever shut down any cloud service offering of this level before (which they have not). This whole "Google loves to shut stuff down" is really tired and overplayed. Go ahead and compare Google's track record with Apple's or Microsoft's, or any other company. They are about on par, yet Google almost always gives 6+ months notice (often over a year), provides one-click alternatives,…
On that list that I've used: Buzz, Pack, Desktop, Reader, iGoogle.
To Be Discontinued: Google Drive Hosting, Google Code.
I don't think it's tired and overplayed. It's a consequence of how Google works; try lots of things and don't be afraid to pull the plug. That strategy is great, and it works.
It's just sometimes the services that are on the edge of being worth Google's time to maintain cause the most backlash because a fair number of people used those services.
Re: Google Cloud Shell
#27Earlier 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.)
Are the different divisions not Google?
But it is more common for a Google product to be completely abandoned, no new features, few bugfixes, etc., as opposed to being actually shut down.
Re: Google Cloud Shell
#28This doesn't actually appear to be new; at least not that I can tell. Google Cloud has supported being able to open an SSH session to any of your instances right from the browser for awhile. I've found it to be a killer feature and am really surprised Amazon Web Services does not offer the same thing.
It's a preconfigured VM that includes all the tools for developing for Google Cloud Platform. You just click a button on a console and you have everything you need, with a 5GB persistent $HOME directory.
True, you could do everything this is doing with Compute Engine. The point is that it's always one-click away and there's no setup, maintenance, or (for the time being) cost.
Re: Google Cloud Shell
#29This is cool, I just want an IRC bouncer.
Re: Google Cloud Shell
#30This doesn't actually appear to be new; at least not that I can tell. Google Cloud has supported being able to open an SSH session to any of your instances right from the browser for awhile. I've found it to be a killer feature and am really surprised Amazon Web Services does not offer the same thing.
It's a preconfigured VM that includes all the tools for developing for Google Cloud Platform. You just click a button on a console and you have everything you need, with a 5GB persistent $HOME directory. True, you could do everything this is doing with Compute Engine. The point is that it's always one-click away and there's no setup, maintenance, or (for the time being) cost.
Ah, makes sense! Thanks for the clarification.
This could be a nice way to isolate operations of production infrastructure. You could go as far as issuing Chromebooks dedicated to the task.