Google Antigravity
641–650 of 1001 posts
Re: Google Antigravity
#642Earlier quoted context omitted.
> It is a vs code fork Google may have won the browser wars with Chrome, but Microsoft seems to be winning the IDE wars with VSCode
I believe our definitions of "winning the IDE wars" are very, very different. For one thing, using "user count" as a metric for this like using "number of lines of code added" in a performance review. And even if that was part of the metric, people who use and don't absolutely fall in love with it, so much so that they become the ones advocating for its use, are only worth a tiny fraction of a "user". neovim won the…
“I never read The Economist” – Management Trainee, aged 42.
Re: Google Antigravity
#643I gave it a fair shot. It is a vs code fork. There were some UI glitches. Some usability was better. Cursor has some real annoying usability issues - like their previous/next code change never going away and no way to disable it. Design of this one looks more polished and less muddy. I was working on a project and just continued with it. It was easy because they import setting from cursor. Feels like the browser wars…
I bet if you sign up for Google AI Ultra for a month your limits will disappear.
It does not.
Re: Google Antigravity
#644Earlier quoted context omitted.
- don't learn from what you tell them Whenever I have a model fix something new I ask it to update the markdown implementation guides I have in the docs folder in my projects. I add these files to context as needed. I have one for implementing routes and one for implementing backend tests and so on. They then know how to do stuff in the future in my projects.
They still aren't learning. You're learning and then telling them to incorporate your learnings. They aren't able to remember this so you need to remind them each day. That sounds a lot like '50 First Dates' but for programming.
Yes, this is something people using LLMs for coding probably pick up on the first day. They're not "learning" as humans do obviously. Instead, the process is that you figure out what was missing from the first message you sent where they got something wrong, change it, and then restart from beginning. The "learning" is you keeping track of what you need to include in the context, how that process exactly works, is up to you. For some it's very automatic, and you don't add/remove things yourself, for others is keeping a text file around they copy-paste into a chat UI.
This is what people mean when they say "you can kind of do "learning" (not literally) for LLMs"
Re: Google Antigravity
#645> Spin up agents to tackle routine tasks that take you out of your flow, such as codebase research, bug fixes, and backlog tasks. The software of the future, where nobody on staff knows how anything is built, no one understands why anything breaks, and cruft multiplies exponentially. But at least we're not taken out of our flow!
After a bunch of people leave the company it's already like nobody knows how anything is built. This seems like a good thing to accelerate understanding a codebase.
Re: Google Antigravity
#646Earlier quoted context omitted.
"junior developers" is a convenient label, it is incorrect but it will take a bit until we come up something that describes entities that: - can write code - tireless - have no aspirations - have no stylistic or architectural preferences - have massive, but at the same time not well defined, body of knowledge - have no intrinsic memories of past interactions. - change in unexpected ways when underlying models change…
You'd also have no intrinsic memory of past interactions if we removed your hippocampus. Coincidentally, the hippocampus looks like a seahorse (emoji). It's all connected.
Not to mention; hippocampus literally means "seahorse" in Greek. I knew neither of those things before today, thanks!
Re: Google Antigravity
#647Earlier quoted context omitted.
I describe them in the claude training I'm doing for my company as: super smart, infinitely patient, overeager interns
Sometimes smart sometimes the opposite, though. Perhaps due to memory loss.
Re: Google Antigravity
#648I remember a previous story months ago about Gemini that had Google PMs trying to hype their product, but it was all question about how nobody knows how to get Gemini API keys with any number of paid subscription.
On top of that how long until it’s https://killedbygoogle.com/ ?
Re: Google Antigravity
#649Earlier quoted context omitted.
I wouldn't bet on an Electron app winning anything long-term in the dev-oriented space.
I strongly disagree. Firstly, the barrier to entry lower for people to take web experience and create extensions, furthering the ecosystem moat for Electron-based IDEs. Even more importantly, though, the more we move towards "I'm supervising a fleet of 50+ concurrent AI agents developing code on separate branches" the more the notion of the IDE starts to look like something you want to be able to launch in an unconfi…
The last thing I want is to install dozens of JS extensions written by people who crossed that lower barrier. Most of them will probably be vibe coded as well. Browser extensions are not the reason I use specific browsers. In fact, I currently have 4 browser extensions installed, one of which I wrote myself. So the idea that JS extensions will be a net benefit for an IDE is the wrong way of looking at it.
Besides, IDEs don't "win" by having more users. The opposite could be argued, actually. There are plenty of editors and IDEs that don't have as many users as the more popular ones, yet still have an enthusiastic and dedicated community around them.