dotGo 2015 - Rob Pike - Simplicity is Complicated

Channel:dotconferences · Length:23:11 · Published:2015-12-02 · Views:172505

Watch on YouTube

Summary

Rob Pike's dotGo 2015 talk argues that Go only seems simple, and that its simplicity hides real complexity that is part of the design. He explains the thinking behind Go's restraint in features.

Why HN recommends it

HN returns to it to explain why Go deliberately resists syntactic sugar and new features.

It's an active choice of the language to not allow many syntactic sugars that make the code have a much higher learning curve. — HN, 2016

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

Subtitles (excerpt)

[Applause] [Music] [Applause] [Music] [Applause] Go which if I translate keep clapping. Of course, those who speak French understand that the translation of that is, "Hello, my waffles." I just learned that this weekend. Um, obviously, Go is successful. I mean, look at this room. Look at what's going on here. Um, and a lot of people have asked why Go is successful or have asked me why Go is successful. And a lot of people have answers that involve tooling or the language or things about it, but I think those are all sort of superficial reasons. I think the real reason is simplicity. Um, Go is simple at least compared to a lot of other languages that are running around at the moment and but simplicity is actually a complicated subject and there are many ways to think about it. Um, last year about May I think I went to a conference hosted by Microsoft called lang.next next and I saw a number of actually quite interesting talks many of which were the leaders of a particular language talking about a new version that was coming out like JavaScript PHP C and so on and I really was struck by one thing about these talks and these languages which is most of the talks consisted of features being added by taking something from another language and adding it to this

On Hacker News

the key is simplicity, you're complaining about language features that allow you to write "fun" code, but remember that we spend around 80% of the time reading or debugging code, the main focus of Go is about writing code that's easy to read which will allow you to scale a project or source code with more people, also remember that easy doesn't mean simple, I think these 2 talks will make you und… — yandrypozo, 2020-08
> Go just hides the complexity from initial inspection. If you (parent, other readers) haven't seen it, Rob Pike's "Simplicity is complicated" is a good discussion of just this point. video: [VIDEO] slides: [LINK] — hartzell, 2020-03
Recently the Go team decided not to add the try-keyword to the language. I'm not a Go programmer and was a bit stumped by the decision until I saw a talk of Rob Pike regarding the fundamental principle of Go to stick to simplicity first. [1] One of the takeaways is, that most languages and their features converge to a point, where each language contains all the features of the other languages. C+… — zubspace, 2019-07
The creators of Go are Rob Pike and Google. I think they would know if a different GC were better and use it. I used to sometimes doubt Rob Pike too and think Go had made some mistakes. After using Go and listening to his talks (like [0]) I realized how wrong I was. There's a reason he has helped build two wildly successful programming languages.. How many have you built? Are you smarter than Goo… — troytchell, 2018-10
To me it feels like apples to oranges comparison. I watched this talk on strangeloop a long time ago, and a version of this talk given on RailsConf recently (watched recently, not given). Here's what I see on the page: > Complex constructs: State, Object, Methods, Syntax, Inheritance, Switch/matching, Vars, Imperative loops, Actors, ORM, Conditionals. > Simple constructs: Values, Functions, Names… — paulriddle, 2018-04

Related videos