# Go: From C++ build waits to the API behind my website

> A 45-minute build sets the scene for Go’s origins at Google. Meet its designers, understand goroutines, and connect the story to my website’s API.

*2026-11-03T17:35:23Z*

How did programmers at Google get tired of waiting and start Go?

In 2007, building one large C++ program there took forty-five minutes. Enough time to make coffee, drink it, and wash the mug! That wait sets the scene for a problem Go addressed: developers’ own time.

## In 60 seconds

Rob Pike, Robert Griesemer, and Ken Thompson began designing Go in 2007; the public announcement followed in November 2009. They wanted simpler development, shorter builds, and tools suited to server software. Goroutines help you organize tasks that make progress concurrently. The API behind my own website is written in Go.

## Where does the 45-minute story come from?

Rob Pike described a 45-minute C++ build in his 2012 Go at Google article and presentation. This was the build time of a particular program, not its runtime or a measurement of every C++ project.

In that same article, Pike calls the scene of Go being conceived during one such build an origin myth. The wait supplies context; it does not prove a precise founding scene or mean the language was completed in 45 minutes. The coffee and mug are our analogy.

## Three designers, a 2007 beginning

The official FAQ dates the initial whiteboard work to 21 September 2007 and names Pike, Griesemer, and Thompson. Griesemer’s account of Go’s evolution includes software complexity, build times, and concurrency among the motivations.

The aim reached beyond one inconvenient wait to a simpler way of developing substantial software. The open-source public announcement came on 10 November 2009, two years after design began.

## Goroutines: more than one request making progress

A goroutine is a function executing concurrently with other goroutines in the same address space. You structure the tasks; the runtime schedules them.

A server can serve requests concurrently. Concurrency does not require every task to execute simultaneously on its own CPU core, and Go does not automatically split arbitrary code into tasks. The net/http documentation provides a concrete server example. Goroutines concern how a program works, rather than explaining its build speed.

## The API behind my website

The API behind my own website is written in Go. That is my personal connection: a request arrives, code handles it, and a response returns. This statement concerns the API, rather than describing the frontend.

Go ranked eleventh in the October 2026 TIOBE index. That is a search-based popularity indicator, not a ranking of quality, execution speed, or job share. The month belongs with the number.

## Learn it if

Learn it if you want to build APIs, servers, and cloud tools. Start with a small server that accepts a request and returns a response, then learn to manage shared tasks and errors. Goroutines make more sense when they solve a problem you understand.

## Frequently asked questions

### Was Go built in 45 minutes?

No. The build wait is context for the problem. Design began in 2007 and the public announcement followed in November 2009.

### Do goroutines run every task at the same instant?

No. They support concurrent progress. Parallel execution across CPU cores depends on the program and its runtime environment.

### Does TIOBE establish that Go is a better language?

No. Eleventh place refers to the October 2026 popularity index, not language quality, program speed, or job opportunities.

## Sources

- [Rob Pike — Go at Google, 2012](https://go.dev/talks/2012/splash.article)
- [Rob Pike — original slides](https://go.dev/talks/2012/splash.slide)
- [Go FAQ — history](https://go.dev/doc/faq#history)
- [Robert Griesemer — The Evolution of Go, 2015](https://go.dev/talks/2015/gophercon-goevolution.slide)
- [Go — public announcement, 2009](https://developers.googleblog.com/go-a-new-programming-language/)
- [Effective Go — goroutines](https://go.dev/doc/effective_go#goroutines)
- [Go — net/http](https://pkg.go.dev/net/http)
- [TIOBE Index — October 2026 edition checked 3 November](https://www.tiobe.com/tiobe-index/)

## Read next

- [Python](https://fadymondy.com/en/blog/why-slow-python-won-ai)
- [JavaScript](https://fadymondy.com/en/blog/javascript-history-why-it-won)
- [Java](https://fadymondy.com/en/blog/java-history-cable-box-deal-android)
- [C++](https://fadymondy.com/en/blog/cpp-history-from-phd-to-arduino)

---

Source: https://fadymondy.com/en/blog/go-history-from-build-waits-to-apis
