HN
Today

A History of IDEs at Google

This post chronicles Google's pragmatic journey from a fragmented developer tooling landscape to a sophisticated, custom-built internal IDE. It details the evolution of Cider, a web-based editor that eventually integrated with VSCode, addressing the unique challenges of Google's massive monorepo. The story highlights how unifying tools, even without strict mandates, ultimately enabled better integrations, extensibility, and the seamless adoption of advanced AI features for internal engineering productivity.

39
Score
4
Comments
#3
Highest Rank
19h
on Front Page
First Seen
May 13, 5:00 PM
Last Seen
May 14, 11:00 AM
Rank Over Time
55356353445677998710

The Lowdown

Laurent Le Brun, a former Google developer tools engineer, offers an insightful history of Integrated Development Environments (IDEs) within Google, focusing on the company's vast 'google3' monorepo. The narrative traces the evolution from a highly fragmented ecosystem where engineers had free choice of tools to the emergence and eventual dominance of a custom, cloud-based IDE named Cider, which later became Cider V by adopting the VSCode frontend.

  • Initial Fragmentation: For years, Google's culture embraced individual engineer choice, with even prominent figures like Jeff Dean arguing against a singular IDE to avoid developer discontent.
  • Productivity Challenges: This approach led to duplicated efforts in integrating Google-specific tools (e.g., Bazel, internal code search) across various IDEs, though Google's internal contribution culture somewhat mitigated this.
  • The Rise of Cider: Around 2016, a new web-based editor, Cider (short for Cloud IDE), gained traction. Initially popular for quick edits by technical writers, it evolved to support developers, solving the problem of slow-loading traditional IDEs and the complexities of Google-scale codebases.
  • Backend Innovation: Cider's core strength lay in its backend, which was designed to index and manage a colossal language graph for the entire monorepo, providing immediate code intelligence despite many commits per second and complex versioning needs.
  • Cider V and VSCode Integration: In 2020, the Cider team made a strategic shift to use VSCode as its frontend. This move leveraged VSCode's maturity, extensibility, and vibrant ecosystem, while retaining Cider's powerful, Google-specific backend, addressing many feature requests instantly.
  • Impact and Unification: By 2023, Cider V was adopted by 80% of Google's main codebase developers. This de facto standardization allowed for significant investment in the tool, fostered the creation of over 100 internal extensions, and facilitated the integration of advanced AI features like Smart Paste and AI code completion.

Ultimately, this history illustrates Google's journey toward creating a highly specialized and effective developer environment. It underscores the profound impact of having a common, extensible platform for enhancing engineering productivity and enabling innovative tooling, even if the path to get there involved a decade of evolution and significant investment.