A history of IDEs at Google
Strong developer-tools and org-design item because it shows how standard internal tooling creates leverage: integrations can be built once, extension work moves to product teams, and AI features become easier to ship on a common platform.
Logged at IST: 2026-07-22 16:07 IST
What it is: Laurent Le Brun’s history of IDEs at Google, focused on google3, Cider, and Cider V.
Gist: Le Brun traces Google’s shift from editor pluralism to a de facto standard internal IDE. The core constraint was scale: local IDE assumptions broke against a billion-file monorepo, shared build, search, review tooling, and a language graph that had to match each developer’s sync state. Cider solved much of this with a web editor backed by centralized indexing, then Cider V adopted VS Code as the frontend so Google-specific backend investment could combine with a mature editor and extension ecosystem.
Newsletter angle: Strong developer-tools and org-design item because it shows how standard internal tooling creates leverage: integrations can be built once, extension work moves to product teams, and AI features become easier to ship on a common platform.