Good videos, with context.
OSCON 2010:  Rob Pike, "Public Static Void"

OSCON 2010: Rob Pike, "Public Static Void"

O'Reilly
3 HN recommenders · discussed 2012–2023
Open YouTube ↗

About this video

A 13-minute OSCON 2010 talk in which Rob Pike argues about what is wrong with mainstream languages like C++, Java and C#, and presents Go as a response. He discusses verbosity and what lightness means in a language.

Why it appears in the archive

HN uses it as a concise statement of the thinking behind Go's design.

AI-generated summary and labels from the source dataset; verify important details against the video. Source & credits.

From the Hacker News discussion

james4k · 2012-11 · rec

>PHP is horribly inconsistent, breaks all the rules about programming language design, and is infuriating. Some say that rules are made to be broken. In the context of Go, Rob Pike argues exactly that in this short talk on why they made Go: [VIDEO]

Read original comment ↗
dottrap · 2014-06 · rec

"Public Static Void" Rob Pike (Bell Labs, Plan 9, Google Go) gave this short speech at OSCON 2010 about what's wrong with programming languages, their thinking, and their recent direction, with a lot of focus on C++/Java/C#, and how Go was a response to that. [VIDEO] Apple Swift seems to share much of the thinking, and the huge enthusiasm for Swift this week suggests developers seem to at least subconsciously recognize there is a problem.

Read original comment ↗
mtrn · 2015-06 · rec

> I wonder what rob pike has to say about OOP or java, I wish I could listen to it. 12 minutes where Pike talks about a few things, that seem to be wrong in our software world: [VIDEO]

Read original comment ↗
mseepgood · 2012-09 · reference

The "Talks and Videos" page ( [LINK] ) is outdated as well. Here's my personal list: Why Learn Go? [LINK] Short interview with Rob Pike, OSCON 2012 Get Started with Go [LINK] Andrew Gerrand A Tour of Go [LINK] Russ Cox Go Concurrency Patterns [LINK] Rob Pike, Google I/O 2012 Goroutines, Channels Meet the Go Team [LINK] Panel (Pike, Thompson, Griesemer, Gerrand, Fitzpatrick, Simons), Google I/O 2012 Computing Map Tiles with Go on App Engine [LINK] Chris Broadfoot, Andrew Gerrand, Google I/O 2012 Go in Production [LINK] Gustavo Niemeyer, Google I/O 2012 Go: Code that grows with grace [LINK] (Contains some audio glitches) Andrew Gerrand Interview with Rob Pike [LINK] Rob Pike, GOTO Conference Lexical Scanning in Go [LINK] Rob Pike Cuddle, A Go AppEngine Demo [LINK] Andrew Gerrand Building Integrated Apps on Google's Cloud Platform [LINK] Andrew Gerrand, Google Developer Day Japan 2011 Real World Go [LINK] Andrew Gerrand, I/O BootCamp 2011 Go: it's that simple?! [LINK] 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 [VIDEO] Rob Pike, OSCON 2010 The Go Programming Language [LINK] Rob Pike, Google Tech Talk

Read original comment ↗
andrewstuart2 · 2017-08 · reference

I guess I'm thinking mostly about the talk Rob Pike gave called "public static void" [1], where he probably describes pretty well what "lightness" means to him, or at least what it meant to him 7 years ago. It seems largely about verbosity. [1] [VIDEO]

Read original comment ↗
bokwoon · 2020-07 · reference

In Go you use the pattern of prefixing enum constants with the enum category to indicate that the enums are related to each other (e.g. StatusOk, StatusNotFound instead of status.OK, status.NotFound). Which is funny because today I came across this quote that "patterns are a demonstration of weakness in a language" in a Go talk [VIDEO] . I wish enums will eventually be implemented, generics are coming after all.

Read original comment ↗
mustache_kimono · 2022-02 · reference

Rob Pike actually defined it exactly this way when it was introduced -- a simpler systems language, in contrast to Java. It's funny -- I actually just watched this video yesterday: [VIDEO]

Read original comment ↗
Yasuraka · 2023-07 · reference

Reminds me of this talk: [VIDEO] And the quote to go along with it: "I'm always delighted by the light touch and stillness of early programming languages. Not much text; a lot gets done. Old programs read like quiet conversations between a well-spoken research worker and a well-studied mechanical colleague, not as a debate with a compiler. Who'd have guessed sophistication bought such noise?"

Read original comment ↗