Google Cloud Platform’s new interactive CLI • Hacker News Board

Re: Google Cloud Platform’s new interactive CLI

#41

Post by cat199 » Fri, Mar 16, 2018, 5:40 PM UTC

puzzle wrote: post #24

NathanKP wrote: post #8

Earlier quoted context omitted.

I don't think its a "l33t" thing its just cultural. A fair number of engineers grew up with old computers that looked like this: https://i.imgur.com/WERwVsS.jpg Personally I learned to code on an old cathode ray tube monitor with green text, hooked up to a Tandy 1000. The CRT made a lot of heat and emitted a faint electronic tonal noise when it was running. I think the use of green color in terminals today is kind of…

The eyes are more sensitive to either yellow-green or blue-green, depending on whether there is light or little of it. Amber/orange/yellow was probably the second most popular choice for terminals back then.

on the down side, if you work on one too long, it fries those particular cones in your eyes pretty good, at least in the case of green and if the contrast is too high..

my daily driver is grey-on-black these days for that reason, though I keep a warm-and fuzzy green-on-black with vt220 font and slow-baud emulator around for the occasional one-off shell command.

Re: Google Cloud Platform’s new interactive CLI

#42

Post by sigjuice » Fri, Mar 16, 2018, 5:42 PM UTC

apetresc wrote: post #30

sigjuice wrote: post #23

I just looked at the first animation. If I find myself typing commands this long, I know I'm doing it wrong.

You must've not used the AWS or GCP CLI tools before... the commands are all very verbose with lots of mandatory parameters. There's really no way to avoid long commands.

I have not. But I have used several other similar CLI tools. I prefer short programs of my own instead of long verbose commands.

Re: Google Cloud Platform’s new interactive CLI

#43

Post by sandGorgon » Fri, Mar 16, 2018, 5:45 PM UTC

optimusclimb wrote: post #28

I wish they would spend more time finishing the halfway done projects they've started (and fully documenting them), rather than continue to launch new ones. For instance...Google CloudSQL - Great! Postgres - Beta...Postgres from AppEngine python...err, we'll get around to it, maybe. Just giving one example, but my point is - finish what you've started before making new. I think recent articles I've read about launchi…

+100 - i was waiting for them to launch Postgres prod. It just doesnt go live. Even worse, they have had trouble in exposing max_connections as configurable PostgreSQL flag (https://issuetracker.google.com/issues/37271935)

Re: Google Cloud Platform’s new interactive CLI

#44

Post by felipelemos » Fri, Mar 16, 2018, 5:59 PM UTC

optimusclimb wrote: post #28

I wish they would spend more time finishing the halfway done projects they've started (and fully documenting them), rather than continue to launch new ones. For instance...Google CloudSQL - Great! Postgres - Beta...Postgres from AppEngine python...err, we'll get around to it, maybe. Just giving one example, but my point is - finish what you've started before making new. I think recent articles I've read about launchi…

It seems that it is the same problem that plagues Google as a whole.

Re: Google Cloud Platform’s new interactive CLI

#45

Post by colemickens » Fri, Mar 16, 2018, 6:17 PM UTC

algorithmsRcool wrote: post #19

jmeyer2k wrote: post #15

AWS also has something similar called AWS Shell: https://github.com/awslabs/aws-shell

Azure has one too https://docs.microsoft.com/en-us/azure/cloud-shell/overview

An interactive CLI (this) is not the really at all the same thing as a JavaScript TTY connected to a container (Cloud Shell).

(Though, Google does also have a Cloud Console that is comparable to Azure's Cloud Shell.)

Re: Google Cloud Platform’s new interactive CLI

#46

Post by ehsankia » Fri, Mar 16, 2018, 6:24 PM UTC

neuland wrote: post #25

This is an interesting accommodation to less terminal savvy users. I'm not interested personally. But, it's an interesting concept. In fact, I think it would be an interesting thing to standardize, like super-completion. Someone else in this thread mentioned that Amazon is working on a similar interactive shell [0], and there is a whole group of tools like this for database CLI's [1], including PostgreSQL, MySQL, MS-…

It's definitely not for less terminal savvy users. If anything, it's for more savvy people, as less savvy people hardly use tab completion, hotkeys and vi/emacs mode. It's meant for power users. Tab completion makes you faster and more efficient. I do agree though that it should be standardized.

Re: Google Cloud Platform’s new interactive CLI

#47

Post by psychometry » Fri, Mar 16, 2018, 6:26 PM UTC

melq wrote: post #31

psychometry wrote: post #22

Still requires Python 2.7, right? What year is it again?

Does it? I don't see that written anywhere, and prompt-toolkit supports python3.

"Cloud SDK runs on Linux, Mac OS X and Windows, and requires Python 2.7.x."

https://cloud.google.com/sdk/downloads

Re: Google Cloud Platform’s new interactive CLI

#48

Post by speby » Fri, Mar 16, 2018, 6:40 PM UTC

optimusclimb wrote: post #28

I wish they would spend more time finishing the halfway done projects they've started (and fully documenting them), rather than continue to launch new ones. For instance...Google CloudSQL - Great! Postgres - Beta...Postgres from AppEngine python...err, we'll get around to it, maybe. Just giving one example, but my point is - finish what you've started before making new. I think recent articles I've read about launchi…

Google is notorious for this behavior. Don't you remember the years-long "beta" status for GMail?

Re: Google Cloud Platform’s new interactive CLI

#49

Post by svolpe43 » Fri, Mar 16, 2018, 6:41 PM UTC

I made something even better. Its for AWS though: https://github.com/svolpe43/cfsh

Re: Google Cloud Platform’s new interactive CLI

#50

Post by azurezyq » Fri, Mar 16, 2018, 6:47 PM UTC

blackaspen wrote: post #32

optimusclimb wrote: post #28

I wish they would spend more time finishing the halfway done projects they've started (and fully documenting them), rather than continue to launch new ones. For instance...Google CloudSQL - Great! Postgres - Beta...Postgres from AppEngine python...err, we'll get around to it, maybe. Just giving one example, but my point is - finish what you've started before making new. I think recent articles I've read about launchi…

This -- _so_ much. That was my first thinking as well. IAM in GCP is still half-baked. How about they finish that? I understand that GCP is a massive engineering effort with endless things going on in series, but core parts of their platform are still mediocre at best. I'd prefer not to see more hackweek projects on their blog.

What feature do you need from IAM?