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

81–90 of 316 posts

Re: Google Workspace CLI

#83

Post by dotancohen »

garciasn wrote: post #14
dotancohen wrote: post #12

Earlier quoted context omitted.

Can you show that the major contributors are employed by Google? I'm not arguing, I'm genuinely asking. Thank you.

https://github.com/jpoehnelt jpoehnelt/README.md About I am a Developer Relations Engineer at Google. Currently I am on the Google Workspace DevRel team and was on the Google Maps Platform before that. Previously I worked at Descartes Labs and the US Geological Survey. Check out my website at https://justin.poehnelt.com .

Thank you!

Re: Google Workspace CLI

#84

Post by jitl »

> quick setup

> requires setting up gcloud cli first, necessitates making a Google Cloud project

cmon google how come even your attempts at good ux start out with bad ux? let me just oauth with my regular google account like every other cli tool out there. gh cli, claude, codex - all are a simple “click ok” in the browser to log in. wtf.

and the slow setup - i need to make my own oauth app & keys??

EDIT: oh yeah and get my oath app verified all so i can use it with my own account

Re: Google Workspace CLI

#85

Post by overfeed »

voidhorse wrote: post #73
laalshaitaan wrote: post #60

[flagged]

Totally. I was just remarking today how funny it is that it was apparently ok for humans to suffer from a dearth if documentation for years , but suddenly, once the machines need it, everyone is frantic to make their tools as usable and well-documented as possible

> everyone is frantic to make their tools as usable and well-documented as possible

Eh, enjoy it while it lasts. Companies are still trying to figure out how to get value by letting a thousand flowers blossom. The walled-garden gates will swing shut soon enough, just like they did after the last open access revolutions (semantic web, Web 2.0, etcetera)

Re: Google Workspace CLI

#86

Post by outlore »

Are integration vendors like Pipedream in trouble now that every company is pushing out MCP servers and CLIs to ride the AI craze? After the Twitter and Reddit API troubles of prior years, I can't imagine any company would willingly bring down the walls of their gardens and give easy access to precious user data. I'm waiting for the rug pull

Re: Google Workspace CLI

#88

Post by nozzlegear »

laalshaitaan wrote: post #60

[flagged]

Is this comment AI generated? I don't like to accuse people of generating comments, but looking at your comment history, almost all of them fit this pattern of a single paragraph with "LLM-isms", this one included (i.e. "the X angle here is real -").

Re: Google Workspace CLI

#89

Post by jitl »

wonderfuly wrote: post #62

Why cli instead of just HTTP API doc? The agent can use curl or write code to send requests.

if nothing else the cli gives very easy access to the HTTP api docs via `gws schema`

i’d rather not waste the context tokens re implementing their cli from scratch, if indeed it does a good job.

Post reply on HN