Does Go Belong to Google?

Does Go Belong to Google? The Question Europe Should Stop Asking

Origins and Ownership

Go was created at Google in 2007 by Rob Pike, Robert Griesemer, and Ken Thompson. Google funded its development, hosts its module proxy, and employs many of its core contributors. By any conventional measure, Go is a Google project.

But conventional measures miss something important about how programming languages actually work. When a language reaches a certain maturity, it stops belonging to its creator. Not legally, not through some transfer of intellectual property, but through the quiet, irreversible accumulation of community investment. Millions of lines of production code, thousands of contributors, hundreds of companies whose critical infrastructure depends on the language continuing to exist and evolve.

Go crossed that threshold years ago. The question is not whether Google created it. The question is whether Google could meaningfully take it away, and the answer is no.

What "Control" Actually Means

Google controls the Go compiler, runs the module proxy, and employs the release team. These facts create a surface-level narrative of dependency that deserves more scrutiny than it typically receives.

The Go specification is open and the compiler is BSD-licensed, which means anyone can fork it, build it, and distribute it without Google's permission or involvement. This is not theoretical. Alternative implementations exist: TinyGo compiles Go for microcontrollers and WebAssembly without using Google's compiler at all.

The module proxy, proxy.golang.org, is a convenience rather than a requirement. Setting GOPROXY=direct tells the Go toolchain to fetch modules from their source repositories, bypassing Google entirely. European organisations can run Athens, an open-source module proxy, on their own infrastructure and after the initial cache warmup their builds never contact Google again. There is no technical reason why a European public Go proxy should not exist, and the Clouds of Europe community is exploring exactly that: a shared go.clouds-of-europe.eu that would give the continent its own module infrastructure, reducing a dependency to an architectural choice rather than a default.

Compare this to genuinely controlled ecosystems. Oracle's Java required licensing negotiations for years. Microsoft's .NET was Windows-only for over a decade. Apple's Swift still cannot build Linux GUI applications without community effort that Apple does not support. Go's BSD license makes these kinds of restrictions structurally impossible.

The European Open-Source Tradition

Europe has a long and underappreciated tradition of shaping the tools it depends on without needing to have created them.

Linux was created by a Finnish student and today it is the foundation of European public infrastructure, maintained by contributors from every continent, governed by a foundation incorporated in the US but operating as a genuinely global institution. No European policymaker seriously argues that Linux is "American software" because the Linux Foundation has a San Francisco address.

The same pattern applies to PostgreSQL, born from a UC Berkeley research project, now the database of choice for European institutions precisely because no single company controls it. The PostgreSQL Global Development Group spans continents and European contributors are not guests in someone else's project. They are co-owners.

Go follows this trajectory. European companies contribute to the compiler, maintain critical libraries, and run significant production workloads. The Go community in Europe is not consuming an American product. It is participating in a global commons.

The Fork as Insurance

Open-source licenses provide a guarantee that proprietary ecosystems cannot: the right to fork. This right is not symbolic, and it has been exercised repeatedly at moments that mattered.

When Oracle acquired Sun Microsystems the MySQL community forked to MariaDB, and European Linux distributions switched within months. When HashiCorp changed Terraform's license from MPL to BSL the community forked to OpenTofu within weeks, and the project is now governed by the Linux Foundation with broad industry backing.

Go's BSD license provides the same insurance. A hypothetical decision by Google to restrict Go would trigger a fork before the announcement finished circulating. The compiler is well-understood, the specification is public, and the community has the expertise to maintain an independent implementation indefinitely. This has never been necessary because Google has no incentive to restrict the language. Go's value to Google comes from its ecosystem: the libraries, the tools, the community of developers who choose it for production systems. Restricting the language would destroy the ecosystem that makes it valuable in the first place.

What Europe Should Actually Worry About

The sovereignty risk in programming languages is not about who created the compiler. It is about lock-in to proprietary ecosystems built on top of the language.

Google Cloud's Go libraries tie applications to GCP. AWS SDK for Go ties applications to Amazon. These dependencies are real sovereignty concerns because they create migration friction by design. The language itself creates none.

European organisations using Go should invest in standards-based libraries, portable abstractions, and infrastructure that runs anywhere. The Kubernetes ecosystem, built almost entirely in Go, demonstrates this principle clearly: the same operator binary runs on GKE, on Scaleway Kubernetes, on a bare-metal cluster in a Dutch data centre. The language does not care where it runs, and neither should the software built with it.

Embracing the Commons

Europe's path forward is not to build European programming languages. That would be an extraordinary misallocation of resources, reinventing a solved problem for reasons of flag-planting rather than engineering.

The path forward is to participate vigorously in global open-source communities: to contribute, to maintain critical libraries, to run shared European infrastructure like module proxies and package mirrors, and to build expertise so deep that these communities cannot function without European involvement. This is how sovereignty works in open-source. Not through ownership, but through indispensability.

Go does not belong to Google any more than Linux belongs to Linus Torvalds or the internet belongs to DARPA. Origins matter for history. Governance and participation matter for sovereignty. Europe should use Go confidently, contribute to it generously, and build production systems on it without apology. The language is a global commons, and Europe's place in that commons is earned through contribution, not guaranteed by geography.