151–160 of 333 posts
The days of using Eclipse were particularly bleak. These days I use Antigravity for the overwhelming majority of my work.
Earlier quoted context omitted.
Although the tool is internal, a lot of information about it is not confidential. As the team had to collaborate with the VSCode team, we got clearance for sharing information about it. The screenshots in the article were posted publicly on GitHub (in vscode issues). You can also find screenshots in https://research.google/blog/smart-paste-for-context-aware-a... More generally, a lot has been communicated on develope…
I'd love for more screenshots should anyone have and can share. I still don't get a great picture of how it's running in the browser and I find UI choices fascinating. But I imagine I'd need an NDA to see the settings/options :')
I think many VSCode users are not familiar with the Comments UI, but it's used in e.g. the "GitHub Pull Requests" extension. Apart from that, some changes in the list of directories/files (for performance reasons) and a redesigned SCM integration.
Earlier quoted context omitted.
My point on the acquisitions was that a surprising amount of their successful software was not made in house. Again, I don't mean it as a knock against them, necessarily. AI is an odd example. For one, a lot of the research there is from acquisitions. Somewhat feeding back to my first point. They also were seen as tripping up on a lot of the current AI race, no?
> My point on the acquisitions was that a surprising amount of their successful software was not made in house. First, that's just not true. Their biggest products by revenue (search/adwords) and biggest stock value driver (AI/Gemini/Datacenters) are clearly in-house creations. But even then, the two biggest "acquisitions" you're probably thinking of are YouTube and Android, acquired in 2006 and 2005 respectively. Wh…
Do these also take a lot of effort to keep going? Absolutely! But that doesn't change that they acquire a ton. They just acquired Wiz this year.
I do question a lot of the focus on a unified IDE when it comes to this strategy. It is not surprising that there is a specific "discontinued google acquisitions" page in wikipedia with that in mind.
Before cider there was Brightly. My recollection was that it was developed by a team in Atlanta and got cancelled before it reached general availability. People were pissed at the time (ex. "cancelling brightly considered harmful"). That died down when Cider delivered on what Brightly had promised. The days of using Eclipse were particularly bleak. These days I use Antigravity for the overwhelming majority of my work…
Very handy for seeing a problem, quickly solving it (sending out a CL) marking it autosubmit and just moving on.
Earlier quoted context omitted.
One important piece of context that might make all these stories less confusing for non-googlers: Code references are less important inside Google editors, because we have a code viewer tool inside the web browser. Most people read, explore, follow references, and share permalinks to the view-only tool. It’s a lot better than viewing code in GitHub. It’s super fast, is connected to language servers and can actually t…
What tools available to the public would you say is similar to this workflow?
Earlier quoted context omitted.
Do they have more success in software products than other companies, though? Most of the software many of us know from them, were acquisitions. They still do heavy acquisitions. Notable that they have double the acquisitions of Amazon. They are on par with IBM. A colossal amount of money spent to make things happen. So, again, are they that much more successful at software than other companies? They have more hilario…
The thing to remember about Google and software is that consumers don't see the vast majority of the software it produces and uses, from the distributed filesystem colossus ( https://cloud.google.com/blog/products/storage-data-transfer... ) to an enormous number of other internal projects just as complicated as that. It's user-facing stuff may or may not be great--and the consumer level flops are legendary--but that…
The biggest question on my mind is how the use of Cider V is being affected by the officially ordained Antigravity. Is the trendline starting to show that its adopting more Antigravity style tooling? or is this causing some sort of rift?
There is a similar internal product but the agentic part is shared between that and Cider.
Was there 2009-2014 and then again 2020-2026. I think there are a lot of aspects of IDE use and culture at Google that this post omits. My recollection from 2009-2011 is that emacs and vim were the dominant editors (just as the TV show Silicon Valley depicted), and there was a decent-sized minority using Eclipse and Intellij, both of which had official support for Google tooling. The command line still largely ruled…
Is Antigravity a Cider-V fork?
Before cider there was Brightly. My recollection was that it was developed by a team in Atlanta and got cancelled before it reached general availability. People were pissed at the time (ex. "cancelling brightly considered harmful"). That died down when Cider delivered on what Brightly had promised. The days of using Eclipse were particularly bleak. These days I use Antigravity for the overwhelming majority of my work…
There was also the code search, uh, I forgot the name "quick change", I believe? Very handy for seeing a problem, quickly solving it (sending out a CL) marking it autosubmit and just moving on.
Earlier quoted context omitted.
Google employees can’t use antigravity. There is an internal version of it which has an agent which is shared between Cider and it.
It's the same thing with a different name and different default settings.