Just a note that you can use opencode with their API gateway (they call it "zen") to get access to all the most popular models using a single account, including gemini. (Although this wouldn't have helped the author, since they wanted to try the Gemini CLI specifically).
I'm using opencode which I think is now very close to covering all the functionality of claude code. You can use GPT5 Codex with it along with most other models.
I'm using tsx for a project to achieve the same effect. As you said, it saves you from having to set up a build/transpilation step, which is very useful for development. Tsx has a --watch feature built in as well, which allows me to run a server from the typescript source files and automatically restart on changes. Maybe with nodemon and this new node improvement this can now done without tsx.
To check types at runtime (if that can even be done in a useful way?) it would have to be built into v8, and I suppose that would be a whole rewrite.
I've switched to opencode. I use it with Sonnet for targeted refactoring tasks and Gemini to do things that touch a lot of files, which otherwise can get expensive quickly.
My heart stopped for a moment when reading the title. I'm glad they haven't decided to axe GPUs, because fly GPU machines are FANTASTIC!
Extremely fast to start on-demand, reliable and although a little bit pricy but not unreasonably so considering the alternatives.
And the DX is amazing! it's just like any other fly machine, no new set of commands to learn. Deploy, logs, metrics, everything just works out of the box.
Regarding the price: we've tried a well known cheaper alternative and every once in a while on restart inference performance was reduced by 90%. We never figured out why, but we never had any such problems on fly.
If I'm using a cheaper "Marketplace" to run our AI workloads, I'm also not really clear on who has access to our customer's data. No such issues with fly GPUs.
All that to say, fly GPUs are a game changer for us. I could wish only for lower prices and more regions, otherwise the product is already perfect.
I used the fly.io GPUs as development machines.
For that, I generally launch a machine when I need it and scale it to 0 when I am finished. And this is what's really fantastic about fly.io - setting this up takes an hour... and the Dockerfile created in the process can also be used on any other machine.
Here's a project where I used this setup:
https://github.com/li-il-li/rl-enzyme-engineering
This is in stark contrast to all other options I tried (AWS, GCP, LambdaLabs). The fly.io config really felt like something worth being in every project of mine and I had a few occasions where I was able to tell people to sign up at fly.io and just run it right there (Btw. signing up for GPUs always included writing an email to them, which I think was a bit momentum-killing for some people).
In my experience, the only real minor flaw was the already mentioned embedding of the whole CUDA stack into your container, which creates containers that approach 8GB easily. This then lets you hit some fly.io limits as well as creating slow build times.
My last position was at Atlassian working on various backend systems, and specifically I've developed (in clojure) the OT-based synchronization engine behind Confluence's collaborative editing feature.
I'm looking to join a company in Japan and would need visa sponsorship.
>Although I am being shown a bunch of accounts to choose from, I am unable to get photos from Google Photos to show on my tv. Not even my own.
The tweet (like almost any similar tweet in my limited understanding) is not clear and void of actual "proper" descriptions of the issue, but it seems like the issue is with "random" images appearing in the "ambient mode screensaver" (whatever it is):
>Private @googlephotos of strangers are being shown to me in the ambient mode screensaver.
