Gemini CLI
691–700 of 820 posts
Re: Gemini CLI
#692An aside, but with Claude Code and now Gemini instrumenting operations with OpenTelemetry by default, this is very cool.
Re: Gemini CLI
#693A few days ago I tested Claude Code by completely vibe coding a simple stock tracker web app in streamlit python. It worked incredibly well, until it didn't. Seems like there is a critical project size where it just can't fix bugs anymore. Just tried this with Gemini CLI and the critical project size it works well for seems to be quite a bit bigger. Where claude code started to get lost, I simply told Gemini CLI to "…
I wonder how much of this had to do with the context window size? Gemini’s window is 5x larger than Cladue’s. I’ve been using Claude for a side project for the past few weeks and I find that we really get into a groove planning or debugging something and then by the time we are ready to implement, we’ve run out of context window space. Despite my best efforts to write good /compact instructions, when it’s ready to ro…
Re: Gemini CLI
#694Re: Gemini CLI
#695"Gemini CLI: your open-source AI agent" I hate this openwashing . It's a closed model, its weights are nowhere to be seen! (not to mention the training data, the real "source" of a LLM) The fact that there is a small component that is open source that accesses this closed model doesn't change that at all.
Re: Gemini CLI
#696They have all hardware and most advanced LLM technology, I don't know why their market value didn't catch up with microsoft.
Wall Street doesn’t like Google. This is the only reason.
Microsoft has a track record of delivering enterprise solutions that dates back to when Page and Brin were toddlers.
Re: Gemini CLI
#697Can't we standardize on AGENTS.md instead of all these specific CLAUDE.md and now GEMINI.md. I just symlink now to AGENTS.md
Hmm kinda makes sense to keep them separate because the agents perform differently, right? You might want to tell Claude not to write so many comments but you might want to tell Gemini not to reach for Kotlin so much, or something. A unified approach might be nice, but using the same prompt for all of the LLM "coding tools" is probably not going to be as nice as having prompts tailored for each specific tool.
Instructions for Claude:
- ...
- ...
Instructions for Gemini:
- ...
- ...
Re: Gemini CLI
#698Been using Claude Code (4 Opus) fairly successfully in a large Rust codebase, but sometimes frustrated by it with complex tasks. Tried Gemini CLI today (easy to get working, which was nice) and it was pretty much a failure. It did a notably worse job than Claude at having the Rust code modifications compile successfully. However, Gemini at one point output what will probably be the highlight of my day: "I have made a…
Unfortunately the CLI version wasn't able to create coherent code or fix some issues I had in my Rust codebase as well.
Here's hope that it eventually becomes great.
Re: Gemini CLI
#699Earlier quoted context omitted.
If you use Node.js your program is automatically too slow for a CLI, no matter what it actually does.
If you even sneeze into performance discussion without providing benchmarks first – you’re a tool.
Re: Gemini CLI
#700Earlier quoted context omitted.
Google Gemini Google Gemini Ultra AI Studio Vertex AI Notebook LLM Jules All different products doing the sameish thing. I don’t know where to send users to do anything. They are all licensed differently. Bonkers town.
Is it really that confusing? Gemini is the equivalent of ChatGPT; AI Studio is for advanced users that want to control e.g. temperature; Vertex AI is the GCP integrated API; Notebook LLM is basically personal RAG; and Jules is a developer agent. Many of these are not even remotely similar.
So Vertex is like AWS Bedrock for GCP?