OK, who wants to put on a GopherCon 2015 next year, dedicated to actual Gopher[1][2][3][4]?<p>I mean, there <i>is</i> a precedent for this sort of thing.<p><a href="http://iubio.bio.indiana.edu/soft/util/gopher/gophercon1.txt" rel="nofollow">http://iubio.bio.indiana.edu/soft/util/gopher/gophercon1.txt</a><p>[1]: <a href="https://en.wikipedia.org/wiki/Gopher_%28protocol%29" rel="nofollow">https://en.wikipedia.org/wiki/Gopher_%28protocol%29</a><p>[2]: gopher://gopher.floodgap.com/<p>[3]: <a href="https://addons.mozilla.org/en-US/firefox/addon/overbiteff/" rel="nofollow">https://addons.mozilla.org/en-US/firefox/addon/overbiteff/</a><p>[4]: gopher://sdf.lonestar.org/
> Ken: lary and sergey came by tonight...<p>> Ken: p.s. one of larrys comments was "why isnt function spelled func?<p>> Rob: fine with me. seems compatible with 'var'<p>> Rob: anyway we can always say, "larry said to call it 'func'"
I really enjoyed the keynote.<p>The joke about the profound error of using whitespace just shows how partisan these discussions are. In go, with the semi-colon insertion rules and with gofmt, there is an implicit whitespace rule all over again.<p>Personally, I like whitespace because its how my mind reads code. Its nice in Python, mostly because of how concise Python is to read. Its a bit of a bind in Java, where you don't trust tools to roll-up functions but on the other hand they all seem so long and full of boilerplate. With gofmt, the go world lives in a significant whitespace world they just don't want to admit it :)
I've wondered what the story was on Go's dependency management, so I'm glad someone brought it up at the end of the keynote. Pike said that it was up to the community to develop tools to deal with that. This is what happened in the Clojure community when Leiningen became the de facto standard, but its dependency management builds on a pre-existing system (Maven). I am curious if this is on anyone's radar, or if it isn't considered a problem.
I am watching the keynote, it looks interesting. I don't know Go at all, though I know several languages including C.<p>I don't quite know what he is talking about when he talks about main and initialization. Can anyone elaborate on this for me?<p>I hate to say this because I feel like a jerk in doing so, but I'm about 25 minutes in and the little gopher that scrolls across the screen (some sort of advertisement, I think) is <i>so</i> distracting. It is awful.
So, in the keynote, Rob underlines again that there'll be no generics. Ever.<p>Path to getting generics thus becomes:<p>1. A preprocessor that eats ggo (generic go) files and emits go. This is is like the original C++ which translated to C for compilation.<p>2. Someone integrates ggo into go to speed it all up.