I am a little disappointed that the conference never asked for feedback afterwards.
While I enjoyed the vast majority of talks, I felt that some didn't hit their mark. A select few speakers were poorly prepared for a conference that they had months to prepare for. One speaker made a comment along the lines of "I would give a demo, but I ran out of time to prepare." Another speaker (verbatim): "I've been working on this talk since yesterday. ... If it looks like I don't know what the next slide is, it's because I don't." There were also 4 talks about the history of go. Three of those talks were given by people that all work closely together. I would have expected to see a higher level of polish in both speaker selection, and preparation by the speakers.
That said, talks I suggest watching:
Simplicity And Go -- This talk is a great counterpoint to everyone that says everything you need is in the stdlib.
Delve Into Go -- A great technical talk about the challenges that golang has with debuggers.
Go GC: Solving the Latency Problem -- Technical talk about the GC changes coming to 1.5.
The many faces of struct tags -- Food for thought on how you can better make use of struct tags. Russ Cox loved the expanded uses.
Dmitry Vyukov - Go Dynamic Tools [1], is the one that stands out to me. The Go-fuzz project which was at the core of the talk was linked earlier today [2]. Gotta love a tool that tells you "here's an obscure bug, RIGHT HERE!"
Thank you for your list. I usually start out thinking I'll watch all the videos from a conference but halfway through the playlist, life happens and I put it off till later. This time I'll watch the ones you've suggested and the others if possible.
There were a lot of great talks at this conference, including one on the new concurrent garbage collector (which is already in beta and hits stable sometime in the next few weeks).
My personal favorite, though, was Katherine Cox-Buday's talk titled "Simplicity in Go"[0]. It's really hard to write a talk that has value for people of all levels of experience (beginner to expert), and this one really stood out to me as an excellent example of one that does.
(Anecdotally, I've been writing Go full-time for 3 years now, and I found the talk valuable, as did a couple of my friends who have been writing Go for only a few months and also attended the conference.)
It's interesting she mentioned Rich Hickey's simple made easy talk. I thought gophers ignored him, because they obviously don't have a problem with mutable state.
Fliam also mentioned Hickey in his talk. It was something about place oriented computing.
No confusion. Hickey seems to strongly dislike mutating shared state. Go doesn't care so much as to enforce that in the language. Hickey is in favor of clear multi-tasking conventions, but go code can do it many ways.
I'm not sure what the first step should be (well, other than setting up a gophersite, reading the RFCs and looking at some implementations), but given that it maps very well to a hierarchical file system, you could position it as a bookmarking tool or something of the sort.
Or you could create an easy way for people to set up their own phlogs and discover others. Position them as convenient alternatives to static site generators while emphasizing Gopher's traits.
Either way, it needs to capitalize on people's discontent with web bloat in some way.
I would die for a simple web server that was more or less like mod_dirlist, but that took markdown (or whatever format) and generated a simple gopher-like navigation structure (basically just the folder hierarchy) with some extra stuff for things like info for each directory and stuff.
Start it, point it to a directory, just upload markdown files and you are up and running. A few simple rules to follow (like the file _info containing a short directory description, some files not being shown on the directory list). Just for getting shit online.
Something like that "motherfuckingwebsite" that gets passed around, but with a simple navigation.
I really enjoyed this conference, specially the talks on CSP, Mobile, The new GC and "What Could Go Wrong". I also hope to see Kelsey Hightower in stage again in GopherCon 2016, he was awesome as MC.
While I enjoyed the vast majority of talks, I felt that some didn't hit their mark. A select few speakers were poorly prepared for a conference that they had months to prepare for. One speaker made a comment along the lines of "I would give a demo, but I ran out of time to prepare." Another speaker (verbatim): "I've been working on this talk since yesterday. ... If it looks like I don't know what the next slide is, it's because I don't." There were also 4 talks about the history of go. Three of those talks were given by people that all work closely together. I would have expected to see a higher level of polish in both speaker selection, and preparation by the speakers.
That said, talks I suggest watching:
Simplicity And Go -- This talk is a great counterpoint to everyone that says everything you need is in the stdlib.
Delve Into Go -- A great technical talk about the challenges that golang has with debuggers.
Go GC: Solving the Latency Problem -- Technical talk about the GC changes coming to 1.5.
The many faces of struct tags -- Food for thought on how you can better make use of struct tags. Russ Cox loved the expanded uses.