TL;DR
Get the latest gadgets delivered free with Prime
- Fast, free delivery on millions of items
- Prime Video, Amazon Music and more included
- Member-only deals all year
Google’s engineers historically used diverse IDEs, leading to fragmentation. Around 2013, a web-based editor called Cider emerged, evolving into Cider V with VSCode frontend support by 2022, aiming for a unified development experience.
Google has significantly transformed its approach to integrated development environments (IDEs), moving from a fragmented ecosystem of tools to a unified, web-based platform known as Cider and its successor, Cider V, supported by VSCode frontend integration.
For years, Google engineers used various IDEs, resulting in a fragmented development environment. In 2011, senior engineers acknowledged the difficulty in standardizing IDEs, citing personal preferences and productivity concerns. Despite this, Google’s culture of organic tooling contributions led to the development of specialized integrations, such as a dedicated IntelliJ team around 2015, to support their large monorepo.
In 2013, Google introduced Cider, a web-based editor designed to facilitate quick editing and code review, especially in a company where many tools are web-centric. Cider’s backend indexed the entire codebase, enabling features like code completion and cross-references, which proved popular among certain developer groups. Over time, Cider’s popularity grew, especially among Go developers, due to its efficient search and reference capabilities.
By 2020, Google decided to adopt the widely used VSCode frontend for Cider, aiming to leverage its mature ecosystem and extendability. The transition involved significant engineering effort, culminating in a beta release in 2021, used by thousands of engineers, with ongoing improvements through 2022.
Why It Matters
This evolution reflects Google’s move toward a more unified, scalable development environment, reducing fragmentation and improving productivity across its engineering teams. The shift to a web-based IDE with VSCode integration is notable because it aligns with modern development practices and could influence IDE strategies at other large tech firms.
As an affiliate, we earn on qualifying purchases.
Background
Google’s main codebase, google3, has historically required strict tooling and conventions for scale. Prior to these developments, engineers relied on diverse IDEs, which posed challenges for large-scale code management. The creation of Cider in the early 2010s was a response to the need for a cloud-based, scalable editing environment that could handle Google’s vast codebase. The move to VSCode in 2020 marked a strategic decision to adopt a more mature, extensible frontend, reflecting broader industry trends.
“Trying to get a group of developers to all agree on a common editor is a recipe for unhappiness. Everyone has different opinions about what is important here.”
— Anonymous Google engineer (source)
“Switching to VSCode as the frontend allowed us to leverage a mature ecosystem and accelerate feature development.”
— Google tech lead (2022)
As an affiliate, we earn on qualifying purchases.
What Remains Unclear
It is not yet clear how widespread the adoption of Cider V will become across all Google engineering teams or how it will evolve further to meet future scale and feature needs.
As an affiliate, we earn on qualifying purchases.
What’s Next
Google is expected to continue refining Cider V, integrating more features, and expanding adoption across teams. Future updates may focus on deeper integration with Google’s internal tools and potentially influencing industry standards for cloud-based IDEs.
integrated development environment for programmers
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Key Questions
Why did Google initially resist standardizing on a single IDE?
Senior engineers believed that forcing uniformity would cause unhappiness, as individual preferences and workflows vary significantly.
What prompted the shift to a web-based IDE like Cider?
The need for scalable, cloud-based editing tools that could handle Google’s massive codebase and support remote, web-centric workflows.
How does Cider differ from traditional IDEs?
Cider is a lightweight, web-based editor that relies on backend indexing of the entire codebase, enabling fast search, cross-references, and code intelligence without the local resource demands of traditional IDEs.
Will Google replace all local IDEs with Cider V?
This remains uncertain; current efforts focus on gradual adoption and feature parity, with the goal of improving developer productivity and consistency.
Fall Picks
fall essentials
As an affiliate, we earn on qualifying purchases.
