It's more the agentic stuff, and things specific to the gemini-cli, which is behind the alternatives in features and capabilities. It was also making an insane number of requests (>1000 in a day, which is about the same as my Copilot usage for a month), but I'm sure they are doing their accounting differently. Google has tried to do AI accounting differently, but has acquiesced to counting tokens instead of chars, fingers crossed they do here to instead of being a snowflake that takes more effort to align in comparisons
I can't stand the cutesiness they've embedded into it either. I don't want that in a work tool
My general sense is that ai-clis will lose out to IDE integrations. I'd prefer a single tool and experience over having to context switch. Putting my AI partner in the same tool and env I use is better than having it separate with hacks to make it seem like it can be in there too, only sorta not quite
I like the Gemini / Gemma family of models
It's more the agentic stuff, and things specific to the gemini-cli, which is behind the alternatives in features and capabilities. It was also making an insane number of requests (>1000 in a day, which is about the same as my Copilot usage for a month), but I'm sure they are doing their accounting differently. Google has tried to do AI accounting differently, but has acquiesced to counting tokens instead of chars, fingers crossed they do here to instead of being a snowflake that takes more effort to align in comparisons
I can't stand the cutesiness they've embedded into it either. I don't want that in a work tool
My general sense is that ai-clis will lose out to IDE integrations. I'd prefer a single tool and experience over having to context switch. Putting my AI partner in the same tool and env I use is better than having it separate with hacks to make it seem like it can be in there too, only sorta not quite