Skip to content
Hallway
0:00 / 0:00

#golang#robpike#concurrency

The Go Programming Language

Google TechTalks

349K subscribers • 56 videos on Hallway

YouTube
  • Recommended by 1 person: 1 on Hacker News.
  • Presented by Rob Pike, co-creator of Go
  • Made by the vendor. The company whose product it covers made or sponsored it.

Intermediate. Assumes working knowledge.

406K views16 years ago1 recommendation

Programming languagesSystems programmingGoLanguage design and type systemsConcurrency and parallelism

Rob Pike introduces Go, explaining its design goals of fast compilation, concurrency, safety, and simplicity.

Google Tech Talks October 30, 2009 ABSTRACT Presented by Rob Pike What is Go? Go is a new experimental systems programming language intended to make software development fast. Our goal is that a major Google binary should be buildable in a few seconds on a single machine. The language is concurrent, garbage-collected, and requires explicit declaration of dependencies. Simple syntax and a clean type system support a number of programming styles. For more on Go including FAQs, source code, libraries, and tutorials, please see: golang.org

Why it's here

1 person recommends this, 1 disputes it

What people say. Pointed to as the original announcement and design rationale for the Go programming language.

ypavanon Hacker News • Recommends

On “Google Go: A New Programming Language That’s Python Meets C++”

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 communication. Efficient, latency-free garbage collection. High-speed compilation. They are aiming at a lightweight type system with no implicit conversions and no more 0x80ULL. A good starting point is their FAQ page and also the tech talk at youtube: link to this video
View on Hacker News

JeanPierreon Hacker News • Disputes

On “Replacing Clever Code with Unremarkable Code in Go”

…e bool is true. A generic set would leave me puzzled and type unsafe1: What types could possibly exist in this set? A set of foos is not that hard to comprehend, and is in fact very much more straightforward to understand than a generic set, which in unfamiliar code may contain anything, or a mapping from foos to bools. 1: Rob Pike mentions in link to this video that type safety is of high importance for Golang, but how does one achieve that if all the different datatypes I implement/need use `interface {}` where I have to cast all values afterwards? That seems very type unsafe, from where I stand.…
View on Hacker News

allenbrunsonon Hacker News • Mentions

On “Why I'm not very excited about Go”

programming languages influence how you think about programming to such a degree that it's difficult to reason objectively about them. it's rare for me to watch long videos, because they are information-poor for the time investment, but i watched rob pike talk for an hour about go this evening. a lot of it is really interesting, but a lot of things about the syntax made me think: ow, that's going to be painful for me if it becomes successful. rob's talk: link to this video
View on Hacker News

devrimon Hacker News • Mentions

On “OOP practiced backwards is "POO"”

thinking OOP as a solution may lead to an article like this whereas it merely is a vehicle. you may or may not use it. problems of OOP is explained in Go Language video by Rob Pike*, however very intellectually stated arguments in this article are mainly false. link to this video
View on Hacker News

mseepgoodon Hacker News • Mentions

On “Will Go be the new go-to programming language?”

…] Andrew Gerrand, OSDC 2011 Practical Go Programming link Andrew Gerrand, FOSDEM 2011 Writing Web Apps in Go link Andrew Gerrand, Rob Pike, Google I/O 2011 Go Programming link Rob Pike, Google I/O 2010 Another Go at Language Design link Rob Pike, Stanford University Public Static Void link Rob Pike, OSCON 2010 The Go Programming Language link to this video Rob Pike, Google Tech Talk…
View on Hacker News

dexenon Hacker News • Mentions

On “Google Go: The Good, the Bad, and the Meh”

For performance of compilation . Go compiles crazy fast -- think two seconds for complete compiler and runtime on a notebook. This provides for rapid hack-compile-debug iterations. link to this video
View on Hacker News

mseepgoodon Hacker News • Mentions

On “Using Rust for an Undergraduate OS Course”

> it seems initially it was meant to be those kind of "systems" From the announcement talk: "And it's a systems language in the sense that we intend it to be used to write things like web servers" link to this video I don't think that Google ever wanted to develop a new OS kernel.
View on Hacker News

andralexon Hacker News • Mentions

On “D for the Win”

Go has been announced as a systems programming language: link to this video . After some backlash the slogan has been changed quietly.
View on Hacker News

legutierron Hacker News • Mentions

On “Three months of Rust”

If I remember properly, when Go was first developed, compilation time was one of the primary metric that Rob Pike et al were optimizing for, and drove major aspects of its design. It shouldn't be surprising that Go blows other systems out of the water in this regard. Here he is talking about it: link to this video
View on Hacker News

hsn915on Hacker News • Mentions

On “I like Odin”

When Go was first announced ~2009, Rob Pike explicitly framed it as a systems language link to this video I would not say it's the same as Java or C#. The crucial difference is that it compiles to a native executable binary file, not something that needs a virtual machine.
View on Hacker News

9rxon Hacker News • Mentions

On “Problems with Go channels (2016)”

…is the one feature in Typescript that doesn't map directly to Javascript. I'm not sure even that one was the settled science back then. Generics were well established at that time, but that one didn't escape the Go authors. From day one it was explicitly called out as a feature Go should have, but that they hadn't figured out how to integrate it. link to this video Despite Taylor's admirably insistent efforts to find a solution (with 8+ proposals to his name, dating back to before Go was released to the public!), it ultimately required convincing an outside expert to lend a hand. > I know others find the type system lacking It may be lacking by today's standards where types are all the rage, but at th…
View on Hacker News

phireon Hacker News • Mentions

On “There is no memory safety without thread safety”

…icit goal, with no carveouts: "Safety is critical. It's critical that the language be type-safe and that it be memory-safe." "It is important that a program not be able to derive a bad address and just use it; That a program that compiles is type-safe and memory-safe. That is a critical part of making robust software, and that's just fundamental." link to this video…
View on Hacker News

phireon Hacker News • Mentions

On “There is no memory safety without thread safety”

…be able to derive a bad address and just use it" Which Go mostly achieves with a combination of garbage collection and not allowing pointer arithmetic. The source of Go's failure is concurrency, which has a knock-on effect that invalidates memory safety. Note that stated goal from 2009 is "good support for concurrency", not "concurrent-safe". 1 link to this video…
View on Hacker News

win311fwgon Hacker News • Mentions

On “Golang proposal: container/: generic collection types”

> 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" — link to this video
View on Hacker News

win311fwgon Hacker News • Mentions

On “Golang proposal: container/: generic collection types”

…nouncement that later turned to "Go might never get generics" dispair. As you'll recall, it finally took convincing Philip Wadler (of Haskell and Java generics fame) to help. Without that lucky break, which almost certainly never would have happened if Go was still some basement project used by nobody, Go probably still wouldn't have generics. 1 link to this video…
View on Hacker News

win311fwgon Hacker News • Mentions

On “Golang proposal: container/: generic collection types”

Huh? First they said they would: link to this 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.
View on Hacker News