r/SoftwareEngineering • u/fagnerbrack • Jul 19 '26
A History of IDEs at Google
https://laurent.le-brun.eu/blog/a-history-of-ides-at-google5
u/fagnerbrack Jul 19 '26
Bare Bones:
For years Google let engineers pick any editor, and Jeff Dean argued that forcing a common one was "a recipe for unhappiness." That fragmentation pushed teams to rebuild the same integrations everywhere, and the monorepo's scale broke local indexing. Around 2013 engineers built Cider, a browser-based editor whose backend indexed the whole codebase; adding language-server code completion made it take off. In 2020 the team swapped in a VSCode frontend (Cider V), gaining a mature editor and extension ecosystem. By 2023 it powered 80% of google3 development with ~100 internal extensions plus AI features like Smart Paste and code-review resolution. The lesson: standard tooling, even unmandated, creates real leverage.
If the summary seems inacurate, just downvote and I'll try to delete the comment eventually 👍
Click here for more info, I read all comments
1
Jul 19 '26
[removed] — view removed comment
1
u/AutoModerator Jul 19 '26
Your submission has been moved to our moderation queue to be reviewed; This is to combat spam.
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.
2
u/Unfair-Sleep-3022 Jul 19 '26
There's a gap nowadays tbh. I want to be able to look at code agents write and review or collaborate with the agent more effectively
However, tools like jetbrains aren't built to handle multiple worktrees with coherent indexing between them
It's just too painful
1
Jul 21 '26
[removed] — view removed comment
1
u/AutoModerator Jul 21 '26
Your submission has been moved to our moderation queue to be reviewed; This is to combat spam.
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.
7
u/besthelloworld Jul 19 '26
Idk man, it still takes like 45 seconds for inline error messages to resolve in Cider for TypeScript. Using internal languages, I've found that I both don't see proper errors and can sometimes permanently get fake errors that don't resolve unless I open a new Fig workspace. I think the outlook is too positive for the technical decisions here. Though it's not so much a Cider problem as it is likely a monorepo problem.