The Go Programming Language

Channel:Google TechTalks · Length:59:26 · Published:2009-11-10 · Views:406554

Watch on YouTube

Summary

Rob Pike's October 2009 Google Tech Talk introducing Go, a new experimental systems language designed for fast builds, concurrency and garbage collection. It covers the goals, syntax and type system.

Why HN recommends it

Used as the primary source for what Go's creators originally promised, such as fast compiles, systems-language framing, safety and generics.

A good starting point is their FAQ page and also the tech talk at youtube — HN, 2009

Programming language design · C, C++, Rust, Go & systems languages

Subtitles (excerpt)

>> PIKE: I’m going to talk about the Go Programming Language, which is going to be--we hope going open source on November 10th, which is in just a couple of weeks. This talk is a little bit before then, so some--there are some future tense for things like links and so on, but everything should be as recorded by the time we actually go public with this stuff. You can see we have a website we’re setting up, which will be the public domain, public viewable domain for that. So, what is it? Well, I’m can talk about all these pieces but it is new, an experimental, concurrent, garbage-collected, systems, language. Experimental because we’re not--we don’t believe this is the answer to everything, but we’re playing and we think it’s gotten to the point where it’s time we should probably tell the world about it. It’s concurrent because it’s really important in the modern world. It’s garbage-collected because we have an opinion on that stuff, which I’ll talk about it quite a bit later. And it’s a systems language in the sense that we intended to be written, to be used to write things like Web servers and other, you know, system aspects like that. You have more control over some things and you have another languages like, say, Java

On Hacker News

From the Tech Talk PDF, it is mentioned that Robert Griesemer, Ken Thompson, and Rob Pike started the project in late 2007. Ian Lance Taylor and Russ Cox joined in 2008. And the goal, as they mention, seems to have the efficiency of a statically-typed compiled language with the ease of programming of a dynamic language but with - Safety: type-safe and memory-safe. Good support for concurrency and… — ypavan, 2009-11
> But looking at how adamant Go used to be on the whole "No Generics" stance What "no generics" stance? Ian Lance Taylor started working on generics before anyone outside of Google had even heard of Go and when the rest of the world found out about Go it was understood that they would come someday. "In short: not yet" — [VIDEO] — win311fwg, 2026-08
Does it? It was only preventable by not releasing Go, which isn't exactly the greatest of solutions. As you know from when Go was first broadcast to the world, they hadn't figured out how to make generics fit[1]. It is not like they weren't trying. Ian Lance Taylor is regarded for beginning work on generics before anyone outside of Google had even heard of Go. "In short: not yet" What was surpris… — win311fwg, 2026-08
Huh? First they said they would: [VIDEO] After a decade of nobody coming up with a solution that did turn to believing that Go would never be able to add generics. That is true. The air of defeat did become quite strong. But the Haskell guy did eventually came along to share his expertise and the rest is history. — win311fwg, 2026-08
> Am I the only one who’s absolutely shocked that Go finally is embracing generics? Yes. Everyone else knows that they were always expected to be included at some point, as told when Go was first announced to the world: [VIDEO] > So what changed? Philip Wadler, of Haskell fame, decided to help? This was well publicized on HN at the time. > I’m not buying the “it took us 20 years to understand how… — win311fwg, 2026-08

Related videos