Live data from Hacker News

A History of IDEs at Google

laurent.le-brun.eu

191–200 of 333 posts

Re: A History of IDEs at Google

#191
When I left Google in the mid 2010s, there were a couple unusual constraints: 1. They had the majority of their code in a vast++ monorepo. 2. There was a policy that forbade having code from this monorepo on your laptop.

Most companies and projects have orders of magnitude less code, and don't restrict where that code can be stored. It's interesting to learn about Cider and the other things Google built to address their unusual situation, but it's worth keeping in mind that their approach probably isn't ideal in ~most modern dev scenarios.

Re: A History of IDEs at Google

#192
post #18

I am very opinionated, but I really don't like Cider V. I have been using neovim at Google since 2017 and it's been great.

same! how do you deal with cloudtop latency though? sometimes my neovim is very slow and laggy because of the remote connection / network file system

Spin up one in the US central region instead of an instance near your satellite office. The bottleneck is usually not your shell connection to the instance but the connections from the instance to all the infrastructure that's mainly based in the US.

Re: A History of IDEs at Google

#193
post #18

I am very opinionated, but I really don't like Cider V. I have been using neovim at Google since 2017 and it's been great.

This is the way.

But the downside is that you do get the Cider team constantly messaging and asking for reasons you won't switch. I gave feedback that their Vim bindings were broken (it would sometimes fail on holding down directional hjkl for no reason) but I'm not sure if they've fixed it since I left in 2023.

Cider is good for writing g3docs though.

Re: A History of IDEs at Google

#195
post #92

Earlier quoted context omitted.

Anyone care to speculate what the internal reasoning is?

Google has a rich history of product mismanagement. It would be a shame and legacy ruined if it were to change.

They just announced the Googlebook (a laptop), not to be confused with Google Books (their service for selling ebooks). It sounds like the mismanagement is right at normal levels.

Re: A History of IDEs at Google

#197

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.

Consumer version:

BE_EVIL=true

Internal version:

BE_EVIL=false

Re: A History of IDEs at Google

#199
This idea of forcing every programmer to use the same IDE is incredibly depressing. I only associate that with really low tier outfits here in NZ, to think that leading companies want to do this too is disheartening (because of course everyone and their dog will copy it).

Fight for your autonomy as a dev, because they will always want to take it away.

Re: A History of IDEs at Google

#200
post #64

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…

Like the most widely used browser and most used mobile phone operating system?
Post reply on HN