351–360 of 369 posts
A bit off-topic, but I (as a non-native reader) find the "anti" in the name off-putting. Has it a special meaning beyond the (meta)physics or is Google just bad with naming?
I always thought it was a joke on the python xkcd: https://xkcd.com/353/ (Which, interestingly, also appears if you type “import antigravity” at the python repl).
> The day was to begin like any other, with Antigravity open > This unexpected shift completely broke my preferred workflow it might not have been so unexpected if you knew you were one of ~15 people that start their day with Antigravity
I think they know.
> The day was to begin like any other, with Antigravity open > This unexpected shift completely broke my preferred workflow it might not have been so unexpected if you knew you were one of ~15 people that start their day with Antigravity
> The day was to begin like any other, with Antigravity open (yes, there are tens of us!) I think they know.
"We should be able to trust that our tools will remain the tools we actually signed up to use." Yep... well that's what free software and open-source is for. You can't trust corporations so you MUST have the actual code. Harsh lesson but at least if something is learned and the mistake not repeated, that's OK.
Earlier quoted context omitted.
Maybe I'm just a cranky old greybeard, but to me, the fact that these CLI tools are written in Node, React, etc. says a lot about the type of devs that are building them
Nobody is getting rewarded for reinventing the wheel.
Earlier quoted context omitted.
Jetski/Antigravity is a better piece of software. The Gemini CLI codebase looks like someone tried to vibe-code a Claude code clone in nodeJS, as it's simply not maintainable. That being said, until recently Gemini CLI was better. It had support for persistent policies on what code could run without asking and had good extension hooks to allow you write extensions that influence policy (to perform complex logic like…
Maybe I'm just a cranky old greybeard, but to me, the fact that these CLI tools are written in Node, React, etc. says a lot about the type of devs that are building them
React, however, I do find questionable, even having read about and understanding the idea behind Ink.
"We should be able to trust that our tools will remain the tools we actually signed up to use." Yep... well that's what free software and open-source is for. You can't trust corporations so you MUST have the actual code. Harsh lesson but at least if something is learned and the mistake not repeated, that's OK.
OSS isn't sufficient. It must also be forkable by a small team. If the software grows complex enough, like Chromium, it doesn't really matter much if the code is open or not.