[IzzyMurad]

Too many Google employees in Hacker News trying to advocate Go...

[tptacek]

Yes. Nobody here wants to learn how Brad Fitzpatrick reasons about, designs, and implements server software. It's all spam.

[drhayes9]

Second this. One of my favorite things is getting a slice, however small, of how truly great programmers get their work done, why they chose what they did, and what the results were.

We actually need more of this on HN, not less.

[ballard]

This doesn't reveal any secrets into systems engineering, but it slices:

    package main

    import "fmt"
    
    func main() {
        cake := make([]byte, 2600)
        copy(cake, []byte("Happy Birthday, Lundberg !"))
        lundberg := cake[:8]
        milton := cake[:0]
        fmt.Println("Lundberg got :", string(lundberg))
        fmt.Println("Milton got :", string(milton))
    }

    // :-)  (Ran out of UTF8 smileys and movie fact checkers).
    // And yes could've used string but bytes are awesomer.

[pjmlp]

Slices aren't Go specific.

[ballard]

Browsing the go goog client source is 30% of it. Go and others could use screencasts of how they fixed production problems, regardless of what lawyers, job security worriers or "hide the dust" folks would say. Mindset is best communicated by solving something real.

http://code.google.com/p/google-api-go-client/source/checkou...

[eliben]

Totally. We should spend more time speculating about every move of Snowden and examining every new piece of fluff in the media about the NSA; linking to actually interesting programming-related content is so 2012.

[pjscott]

Are you speculating about a conspiracy? Or just voicing some vague, unfocused resentment?

[IzzyMurad]

speculating a conspiracy.

[gillianseed]

I have no affiliation with either Google or Mozilla but I pretty much always upvote articles concerning Go and Rust simply because I'm interested in those languages and want to encourage more articles about them to be posted.

[microtonal]

At some point there were quite many Go articles without much substance. These articles were also very predictable. The positive articles contain pretty much the same enumeration of Go features (goroutines, channels, imports, etc.) or how they rewrote a five year old, now well-understood, failing Python subsystem in Go and have massive improvements (surprise). The negative articles pretty much all complained about how not using an import results in a compilation error (surprisingly, the lack of generics are only mentioned in comments ;)).

But these slides were genuinely interesting to pretty much the whole HN audience: it covers architecture decisions, the effect of code rot, the breadth of the Go standard library, a new object caching system, and a real-world example of Go usage.

tl;dr even to someone who is a bit critical towards Go (ie. me), it was a very interesting read.