Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

A History of IDEs at Google

laurent.le-brun.eu

Post reply on HN
Print view View original

171–180 of 333 posts

Re: A History of IDEs at Google

#171

Post by VirusNewbie »

taeric wrote: 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…

If GCP was its own company it would almost be a Fortune 50 company on its own. Youtube would be a Fortune 100 company. That seems a lot more successful than most software companies.

Meta on the other hand, really just has ads.

Re: A History of IDEs at Google

#172

Post by lunarboy »

phreeza wrote: post #38

The most amazing thing to me about Cider-V was that Cider (without the V) actually went away after a relatively short amount of time, when virtually every other internal service that is officially EOL-ed lives on essentially forever.

I feel like core dev team learned a lot about actually enabling a web based ide for line 100k engineers across the globe for a gazillion line mono repo. ciderv is really just a skin for the amazing infra. Which is also why I think there was less resistance to the change

Re: A History of IDEs at Google

#173

Post by fragmede »

richardboegli wrote: post #142
materielle wrote: post #128

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?

https://github.com/jhuangtw/xg2xg has a broader list

Re: A History of IDEs at Google

#174

Post by lunarboy »

keeda wrote: post #62
StilesCrisis wrote: post #5

"the advantages of having a single, extensible platform become even more obvious" -- imagine the impact that could be unlocked if we got the Android and Chromium workflows into CiderV/Critique! The article is framed around "all Googlers" but there is still a very large contingent of Googlers who cannot use these tools.

I would imagine Android development, with its reliance on simulators for local UI testing, is pretty complicated to shoehorn into a web-based IDE? I think cloud-based IDEs would only really work for anything for which a text or web-based UI suffices. (Which is already quite a lot: that covers code, logs and web pages.) For anything with native UIs, I suppose you could "remote desktop" into an app or a simulator runni…

iOS apps at google are developed via ciderv that had a connection to your local mac, and it's amazing. All code editing is "online" and builds are cached, but simulator runs on your local machine. I'm convinced the apple dev env at google is like 100x better than apple's

Re: A History of IDEs at Google

#175

Post by InfiniteRand »

computerdork wrote: post #106
DannyBee wrote: post #100

Earlier quoted context omitted.

That is because the Cider team did an amazing job of managing it, and spent tons of time going bug report by bug report to find and fix the blockers stopping people from preferring Cider-V over Cider, instead of the typical Google deprecation approach of "monkey knife fight"

haha, that's a great way to put it! And I get the overall gist of it, but why monkeys? :)

Because it's international waters

Re: A History of IDEs at Google

#176

Post by jvolkman »

randomCloud wrote: post #160
kridsdale3 wrote: post #140

Earlier quoted context omitted.

It's the same thing with a different name and different default settings.

Are they actually cut from the same codebase? The internal version has workspace support and other features cut from Cider I assume

The settings in the internal version are "Antigravity User Settings". Pretty sure they're the same.

Re: A History of IDEs at Google

#178

Post by jvolkman »

laurentlb wrote: post #70
skybrian wrote: post #58

> 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).

IntelliJ was unsupported ("community supported") when I joined in the summer of 2015. I built a new protobuf editor plugin during that period as a side project, mostly for myself, which suddenly became used by thousands of Googlers when IntelliJ became the supported IDE again in ~2016?

I eventually handed it over to JetBrains and I think it ships by default with IntelliJ now.

Re: A History of IDEs at Google

#179

Post by malkia »

Xoogler here (2014-2017). My team (part of Ads) used primarily Java, and we used the Eclipse, then we started switching the IntelliJ.

Cider was used also a lot, but I've heard even back then some folks were free to use whatever they like - vi, emacs, you name it.

Re: A History of IDEs at Google

#180

Post by malkia »

bsimpson wrote: post #50
AJRF wrote: post #11

Earlier quoted context omitted.

What is Google3?

It's a monorepo, which is a bunch of libraries (in this case, the code for most Google products) in a single repository. Those libraries can have dependencies on each other. One is a framework called Wiz, which renders the frontend for a bunch of Google web apps. You can imagine that the Wiz team might want to refactor an API, but not have to worry about different apps using different versions. In a monorepo, they ca…

yup - when I started in 2014, coming from long gamedev experience it was nice that "g4" was just "p4" rewritten for piper. (alzo "blaze menu" was cool, but did not show (AFAIR) places in LAX)....
Post reply on HN