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

Google Workspace CLI

github.com

Post reply on HN
Print view View original

101–110 of 316 posts

Re: Google Workspace CLI

#101

Post by m8s »

virgildotcodes wrote: post #95

God, getting this set up is frustrating. I've spent 45 minutes trying to get this to work, just following their defaults the whole way through. Multiple errors and issues along the way, now I'm on `gws auth login`, and trying to pick the oAuth scopes. I go ahead and trust their defaults and select `recommended`, only to get a warning that this is too many scopes and may error out (then why is this the recommended set…

I’ve been really unhappy with pretty much every Google product I’ve used except their consumer productivity tools — Gmail, Calendar, and Meet. Diving into Google Cloud has been extremely unsatisfactory

Re: Google Workspace CLI

#102

Post by jen20 »

hoppp wrote: post #90
laalshaitaan wrote: post #60

[flagged]

Google will slowly win at the AI game. They got everything going, lots of free usage and they are keeping it real, unlike openAI that rides a hype train

They're going to have to significantly up their game - IIUC, you can't use a Gemini subscription with OpenCode anymore, and the Gemini CLI is such utter trash that it's unusable (it doesn't even have a plan mode in the preview releases, and can barely maintain a connection to a server).

Re: Google Workspace CLI

#103

Post by varenc »

virgildotcodes wrote: post #95

God, getting this set up is frustrating. I've spent 45 minutes trying to get this to work, just following their defaults the whole way through. Multiple errors and issues along the way, now I'm on `gws auth login`, and trying to pick the oAuth scopes. I go ahead and trust their defaults and select `recommended`, only to get a warning that this is too many scopes and may error out (then why is this the recommended set…

Similar frustrations. I was only able auth using some Google app I created for an old project years ago that happened to have the right bits.

It wild that this process is still so challenging. There's got to be some safe streamlined way that sets up an app identity you own that can only use to access your own account.

My guess is that organizationally within Google, the developer app authorization process must have many teams involved in its implementation and many other outside stakeholders. A single unified team wouldn't responsible for this confusion and complexity. I get why... it's a huge source of bad actors. But there's got to be a better way.

Re: Google Workspace CLI

#104

Post by brightball »

m8s wrote: post #101
virgildotcodes wrote: post #95

God, getting this set up is frustrating. I've spent 45 minutes trying to get this to work, just following their defaults the whole way through. Multiple errors and issues along the way, now I'm on `gws auth login`, and trying to pick the oAuth scopes. I go ahead and trust their defaults and select `recommended`, only to get a warning that this is too many scopes and may error out (then why is this the recommended set…

I’ve been really unhappy with pretty much every Google product I’ve used except their consumer productivity tools — Gmail, Calendar, and Meet. Diving into Google Cloud has been extremely unsatisfactory

I ran a project for a company on Google Cloud a few years ago and enjoyed it once I got used to everything. I’d use it more now if they had better low end pricing to start projects there.

It’s a very different experience than AWS though and takes some getting used to.

Re: Google Workspace CLI

#105

Post by bigstrat2003 »

varenc wrote: post #30
betaby wrote: post #26

I'm curious why `npm` is used to install a `rust` binary?

I found that strange as well. My guess is that `npm` is just the package manager people are most likely to already have installed and doing it this way makes it easy. They might think asking people to install Cargo is too much effort. Wonder if the pattern of using npm to install non-node tools will keep gaining traction.

Most people aren't going to have npm installed though. Nobody outside of web devs uses it.

Re: Google Workspace CLI

#106

Post by freakynit »

varenc wrote: post #51
freakynit wrote: post #41

Earlier quoted context omitted.

Why not just downloadable binary then?

For many, installing something with npm is still easier. It chooses the right binary for your OS/architecture, puts it on your PATH, and streamlines upgrades. Their Github releases provides the binaries, as well as a `curl ... | sh` install method and a guide to use github releases attestation which I liked.

Hmm, that's right... thanks..

Re: Google Workspace CLI

#107

Post by SV_BubbleTime »

jitl wrote: post #93
hoppp wrote: post #90

Earlier quoted context omitted.

Google will slowly win at the AI game. They got everything going, lots of free usage and they are keeping it real, unlike openAI that rides a hype train

yeah just like they’ve slowly won at cloud over AWS and Azure. oh wait

Remember that time they used their network effects to auto-enroll all Gmail users into their Facebook competitor and instantly won?

Re: Google Workspace CLI

#108

Post by bigstrat2003 »

brunoborges wrote: post #33
betaby wrote: post #26

I'm curious why `npm` is used to install a `rust` binary?

NPM as a cross platform package distribution system works really well. The install script checks the OS and Arch, and pulls the right Rust binary. Then, they get upgrade mechanism out of the box too, and an uninstall mechanism. NPM has become the de facto standard for installing any software these days, because it is present on every OS.

> NPM has become the de facto standard for installing any software these days, because it is present on every OS.

That's not remotely true. If there is a standard (which I wouldn't say there is), it's either docker or curl|bash. Nobody is out there using npm to install packages except web devs, this is absolutely ridiculous on Google's part.

Re: Google Workspace CLI

#109

Post by vishnugupta »

tedk-42 wrote: post #5

Haha in the world of AI/MCPs, all of a sudden we have a push for companies to properly build out APIs/CLI tools.

But on the other hand a (possibly dark) pattern is emerging where companies are asking you to upgrade to a higher plan to access MCP.
Post reply on HN