←back to thread

Gemini CLI

(blog.google)
1336 points sync | 2 comments | 25 Jun 25 13:10 UTC | HN request time: 0.419s | source
Show context
ZeroCool2u ◴[25 Jun 25 13:39 UTC] No.44377226[source]▶
Ugh, I really wish this had been written in Go or Rust. Just something that produces a single binary executable and doesn't require you to install a runtime like Node.
replies(12): >>44377273 #>>44377286 #>>44377337 #>>44377341 #>>44377366 #>>44377649 #>>44377914 #>>44378962 #>>44380417 #>>44382222 #>>44384234 #>>44384426 #
iainmerrick ◴[25 Jun 25 13:43 UTC] No.44377273[source]▶
Looks like you could make a standalone executable with Bun and/or Deno:

https://bun.sh/docs/bundler/executables

https://docs.deno.com/runtime/reference/cli/compile/

Note, I haven't checked that this actually works, although if it's straightforward Node code without any weird extensions it should work in Bun at least. I'd be curious to see how the exe size compares to Go and Rust!

replies(4): >>44377313 #>>44377346 #>>44377642 #>>44377877 #
ZeroCool2u ◴[25 Jun 25 13:48 UTC] No.44377313[source]▶
Yeah, this just seems like a pain in the ass that could've been easily avoided.
replies(2): >>44377374 #>>44377485 #
jstummbillig ◴[25 Jun 25 14:04 UTC] No.44377485[source]▶
It feels like you are creating a considerable fraction of the pain by taking offense with simply using npm.
replies(1): >>44377667 #
1. evilduck ◴[25 Jun 25 14:22 UTC] No.44377667[source]▶
As a longtime user of NPM but overall fan of JS and TS and even its runtimes, NPM is a dumpster fire and forcing end users to use it is brittle, lazy, and hostile. A small set of dependencies will easily result in thousands (if not tens of thousands) of transitive dependency files being installed.

If you have to run end point protection that will blast your CPU with load and it makes moving or even deleting that folder needlessly slow. It also makes the hosting burden of NPM (nusers) who must all install dependencies instead of (nCI instances), which isn't very nice to our hosts. Dealing with that once during your build phase and then packaging that mess up is the nicer way to go about distributing things depending on NPM to end users.

replies(1): >>44382382 #
2. frollogaston ◴[25 Jun 25 22:34 UTC] No.44382382[source]▶
I ran the npm install command in their readme, it took a few seconds, then it worked. Subsequent runs don't have to redownload stuff. It's 127MB, which is big for an executable but not a real problem. Where is the painful part?