In this post by +Brett Slatkin, he talks about the orthogonality of features in Go (he calls it "emergent behavior", which is the wrong term). Orthogonality of features in a programming language is hard to achieve, and we worked hard to achieve it, so I'm glad he appreciates that.

I was struck, though, by this comment from John Haugeland:

"Gasp! A bunch of stuff you can do in most languages, and a misunderstanding of what emergent behavior is, presented by an author who doesn't realize this is all old hat. Truly, that is the power of go."

He means this a snide dig, of course, but it's true. It is old hat. The thing is, he doesn't appreciate that the service he's using to write that comment is written by programmers, not as facile in some of the more abstract languages and mathematical notions as he is, for which these ideas are not old hat. And making these (and other) ideas available to working programmers as opposed to programming language researchers is indeed the "power of go". And that, too was deliberate.

So I accept his barb, and acknowledge it with a smile.

Gophercon was awesome, by the way.
I just got back from Gophercon and had a great time. One of my favorite sessions was Q&A with the Go team. Rob, Andrew, Brad, and Robert took questions from the audience for an hour. By far the best question was "What was the first thing you saw in Go that surprised you?" Here is what I learned.
Shared publiclyView activity