A History of IDEs at Google

Google has transitioned its internal development environment from a fragmented ecosystem of various IDEs to a unified, cloud-based platform centered around VSCode, significantly improving developer productivity and standardization.

For many years, Google’s engineers used different IDEs, which created challenges in maintaining consistent tooling across the company’s vast codebase. In 2011, senior engineers concluded that unifying IDEs was impractical due to differing preferences and opinions. Instead, Google encouraged organic development of internal tools, resulting in a variety of integrations for code search, formatting, and build tools.

Starting around 2013, Google developed Cider, a web-based editor designed to handle the scale and unique tooling of Google’s monorepo. Cider became popular for quick edits and code review, leveraging a backend indexing system that managed the entire codebase’s data. Over time, Cider added features like code completion via the language-server protocol, making it more appealing to developers.

In 2020, Google’s internal team decided to adopt VSCode as the frontend for Cider, leveraging its mature ecosystem, extensibility, and familiarity. By 2022, a complete transition was underway, with a beta version used by thousands of engineers. The move aimed to unify the development experience, reduce maintenance overhead, and improve integration with existing tools like version control and code review systems.

Why It Matters

This shift represents a major change in Google’s developer infrastructure, moving from a fragmented, internally built IDE ecosystem to a standardized, cloud-based environment based on widely adopted tools. It enhances developer productivity, reduces duplication of effort, and improves consistency across teams, which is critical given Google’s scale.

Background

Google’s monorepo, google3, has been central to its engineering efforts since the early 2010s. The company historically prioritized strict tooling and conventions to support scale, but allowed engineers to choose their preferred IDEs, leading to fragmentation. The development of Cider and its evolution reflects Google’s response to the challenges posed by the size and complexity of its codebase, and the need for a scalable, efficient development environment.

“The move to VSCode was about leveraging a mature, extensible platform that could unify our tooling and improve developer productivity at scale.”

— Former Google engineer involved in Cider development

“Cider’s backend indexing system was crucial in handling Google-scale codebases, enabling fast, accurate code intelligence.”

— Google internal project lead

What Remains Unclear

Details about the full scope of the transition, including how all teams have adopted the new environment, remain unclear. Specific timelines for complete migration and potential future features are still being developed or announced.

What’s Next

Google plans to continue refining its VSCode-based platform, expanding features, and integrating more tools. Further updates on adoption rates and user feedback are expected in the coming months.

Key Questions

Why did Google initially avoid a unified IDE?

Senior engineers believed that forcing a single IDE would cause dissatisfaction due to differing preferences and priorities among developers.

What was Cider, and why was it important?

Cider was a web-based editor developed at Google to handle code editing at scale, offering fast access and integration with Google’s internal tools, becoming popular among engineers.

Why did Google switch to VSCode as the frontend?

VSCode’s maturity, extensibility, and widespread adoption made it an ideal choice to unify the development environment and leverage existing features and extensions.

What are the benefits of this transition for Google engineers?

It improves consistency, reduces maintenance overhead, speeds up development workflows, and enhances integration with internal tools and systems.