GopherCon 2015 videos
youtube.com
youtube.com
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.
This is, sadly, normal for conferences.
There is a reason why if you are a remotely competent event speaker, everybody in the universe will start inviting you.
[1] https://www.youtube.com/watch?v=a9xrxRsIbSU&index=7&list=PL2...
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.)
[0]https://www.youtube.com/watch?v=S6mEo_FHZ5Y&index=5&list=PL2...
Fliam also mentioned Hickey in his talk. It was something about place oriented computing.
https://en.wikipedia.org/wiki/Gopher_%28protocol%29
There are probably people reading this who were born well after Gopher's heyday.
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.
Really? Any evidence to support this? I'm curious.
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.
https://httpd.apache.org/docs/2.2/mod/mod_autoindex.html#hea...
There is probably a way to combine modules to get it to render markdown in place of HEADER.html
Uriel would have been very proud to see this day. Rest in peace.
:P