Rob Pike about the target group of the Go programming language (golang)
f8C4G86p KbqEFe470 HN recommenders · 2023–2024
7K views · talk · evergreen · Uploaded 2020-01-13
A short excerpt of Rob Pike's Lang.NEXT 2014 talk where he describes Go's target audience as young Google programmers who are not researchers. The language has to be easy for them to understand and adopt.
Cited to show who Go was designed for, often in critiques of the language's simplicity.
49:55How Python was Shaped by leaky Internals, Armin Ronacher, Flask framework
Видео с мероприятий {speach!
1:12:27CppCon 2015: Andrei Alexandrescu “std::allocator...”
CppCon
51:18Lexical Scanning in Go - Rob Pike
GoogleFOSSSydney
46:09Why Isn't Functional Programming the Norm? – Richard Feldman
Metosin
1:03:29Maybe Not - Rich Hickey
ClojureTV
7:48Conway's Game Of Life in APL
Dyalog
1:12:56Lecture 1A | MIT 6.001 Structure and Interpretation, 1986
MIT OpenCourseWare
1:42:09Crockford on JavaScript - Volume 1: The Early Years
YUI Library
3 comments from Hacker News
Here you go: [VIDEO] I think Go could still work without completely neutering the type system. Algebraic Data Types and pattern matching are not difficult... python already has them.
It's Go. The description fits well, and it's pretty much confirmed by the Rob Pike quote in the sidebar. [VIDEO]
> It's more likely that the person re-implementing the SSO flow is making a mistake The thread has other people confirming the same behaviour - and the description of the issue (preventing a double-submit of a non-idempotent action) is something most web-focused developers learn in their first year. I don't understand why people assume that the people working at Google/etc are inherently incapable of producing bugs. Go literally invented a new programming language to make their staff less likely to fuck up because they don't have much real world experience: [VIDEO]