Live data from Hacker News

A History of IDEs at Google

laurent.le-brun.eu

81–90 of 333 posts

Re: A History of IDEs at Google

#81

Earlier quoted context omitted.

Is Antigravity a Cider-V fork?

I don't think so, I think they forked VS Code directly or possibly forked Windsurf which forked VS Code. Hence the turf war and internal controversy; a lot of the effort on Cider-V got dropped on the floor, right at the height of Cider-V's popularity when they were getting large amounts of features. Duckie does still exist, and is probably one of the most used (and useful) AI tools at Google. Yes, it's just a Gemini…

[deleted]

Re: A History of IDEs at Google

#82

Meanwhile Google acquired windsurf, released antigravity, and recently handicapped it for Google business workspace users by removing the AI Ultra plan for workspace. So the only real way to use antigravity is either being a Google employee or using a personal account and AI Ultra. https://knowledge.workspace.google.com/admin/gemini/ai-ultra...

It was a sad surprise last week when we tried to upgrade the workspace AI plan for some of our team members to Ultra and it was gone. We're moving to Claude/Codex.

Re: A History of IDEs at Google

#83
I can't imagine people enjoying web based IDEs. I used to work for a company that has everything made internally, including IDE -- they used the same method OP described -- using VSCode on web. The experience is horrible.

I guess maybe it was fancy back in mid 2010s, but my experience was a couple of years ago.

Re: A History of IDEs at Google

#84

I was surprised to read that Chromebook use at Google was common for engineers. Even if developing remotely I had assumed they'd opt for the most powerful machine possible.

How common? I'd wager most people still use a mac, followed second, but far by regular goobuntu laptops. Chromebooks goes 3rd because Windows is practically banned.

> Windows is practically banned.

FWIW I don't think this is accurate (was kinda true in the 2010s?). I wouldn't be surprised if it's almost easier to get windows laptop than linux one now.

Re: A History of IDEs at Google

#85

> a team dedicated to the IntelliJ integration was formed around 2015 I don't know which team that was, but to add to that, official support for IntelliJ at Google started quite a bit earlier. I was the second person to join a team writing IntelliJ plugins. We wrote a Blaze plugin not too long after Blaze launched, as it was becoming more popular. Google tells me that Blaze launched in 2006, so I think it must have b…

I'm not sure about the dates. At some point (2014?), the use of IntelliJ was discouraged in favor of Eclipse. One year later or so, the decision was reversed and the effort focused on IntelliJ (and Eclipse were considered deprecated).

Was there never a detour via Eclipse Theia? I thought it might have had some traction internally, since Cloud Shell is based on it.

Re: A History of IDEs at Google

#87

I was surprised to read that Chromebook use at Google was common for engineers. Even if developing remotely I had assumed they'd opt for the most powerful machine possible.

Very little development in Google3 happens locally. You aren't even allowed to keep the source code on your local disk, and this is true no matter what OS it runs. (Android and Chromium are different though.) You have access to an extremely powerful remote workstation that from a UI perspective functions almost identically to a local workstation, via Chrome Remote Desktop. Plus, no one builds things locally, even on…

I can understand Android (including the Linux kernel) being "too big" and "too separate" to go into Google3, but why Chromium? When it was forked from KHTML/WebKit it was probably not that big compared to the rest of Google's codebase.

Re: A History of IDEs at Google

#88

Earlier quoted context omitted.

How many new googlers use vim or emacs do you think? I can imagine at least a small amount of new vim people since vim will always be popular, but I would love to know if more than a handful of new googlers a year use emacs

I joined gdm recently, and previously used (neo)vim exclusively. Begrudgingly Cider-V is very, very good. It might be possible to get by without it, but the system is so locked down you’re going to make a lot of sacrifices. (very few authorised extensions, codebase is so large it’s going to break whatever tools your used to using anyway, no git) I’m well thinking I may as well trade my brick of an m5 pro for a 13” ch…

> codebase is so large it’s going to break whatever tools your used to using anyway, no git

There is Jujutsu (with Piper backend) officially supported, and that is better than git. But of course, you will not be grepping the source code, there is code search for that.

Re: A History of IDEs at Google

#89
post #12

The advantages of a single platform are as obvious as the disadvantages. In that they are often whatever you want to frame them as for a narrative. I do think Google will continue to get results out of their tooling, as long as they are investing in the tooling. But that is not zero cost. Is it worth it for what they are doing? Largely seems to be. But it isn't like they are that much more successful at software proj…

The catch is that you need to build good software so people use it so that you can show ads

Re: A History of IDEs at Google

#90

I can't imagine people enjoying web based IDEs. I used to work for a company that has everything made internally, including IDE -- they used the same method OP described -- using VSCode on web. The experience is horrible. I guess maybe it was fancy back in mid 2010s, but my experience was a couple of years ago.

From the article: “ Cider was a light client that opened much faster than traditional IDEs. All the magic happened on a backend that indexes the entire codebase, so that all the data was ready whenever someone opened the webpage. ”

Sounds like all other editors were slow compared to Cider.

Post reply on HN