text
stringlengths
0
1.49k
• Static Check by Dominik Honnef
• ZIM by Matt Hamilton
• Discussion of Zsh shell and its features compared to Bash
• Release announcements for Go 1.7.5 and Go 1.8rc3
• Preview of upcoming changes in Go 1.9 and discussion of Go 2.0 proposals
• Mention of a possible JVM backend for Go
• Brief history of the Go cross-compiler and gccgo
• Embarrassing moments from past GopherCon events
**Erik St. Martin:** Welcome back everybody to another episode of GoTime. It is episode number 32. We are recording this today on January 26th. Today's show is sponsored by StackImpact and Ardan Labs series of Go training. Today on the show we have myself, Erik St. Martin, Brian Ketelsen is also here - say hello, Brian...
**Brian Ketelsen:** Hello, Brian.
**Erik St. Martin:** And Carlisia Pinto.
**Carlisia Thompson:** Hi, everybody.
**Erik St. Martin:** Our special guest today is Filippo Valsorda. Why don't you give everybody kind of a quick background about yourself? Tell us a little bit about yourself and the things you're working on, and then we'll kind of get into some of the projects you've been working on.
**Filippo Valsorda:** Hello, everyone. I'm Filippo, I'm from Italy and I work at CloudFlare. I did a number of different things with Go at CloudFlare. The most recent one is a small project that I recently published, called hellogopher. Before that, I was working on the CloudFlare DNS server, which is pure Go.
**Erik St. Martin:** Recently we've been looking at one of your projects, which was the hellogopher, which was kind of an easy way to bootstrap a project for people who might not be familiar with using GOPATH. Do you wanna talk a little bit about that?
**Filippo Valsorda:** Sure. At CloudFlare we are hiring a lot of developers, and we don't really hire Go developers; we hire developers, and then we train them to work on Go, because you know how nice and easy it is to pick up the language.
So I've been looking at how to smooth that process and also how to make it easier for other people in the company to interact with all these repositories that are in Go when they're not Go developers. I was going through this process, and then on a drive home from Napa, with a lot of wine involved. I was in a car with ...
**Erik St. Martin:** Yeah, it's funny because it was yesterday or the day before I had a friend who had a similar issue with "Where do you check out the code to?" because most of the time you're used to just pulling it to wherever you happen to store your code. It doesn't have to be in a specific spot on your hard driv...
Then the other side of it that gets confusing is how to you contribute back? That's a common confusion... Like, "Okay, I wanna commit something, so I fork this repo, but now it's not in the right place... How do I change my import path?" and it's not immediately clear that you could just set your fork as a different re...
**Filippo Valsorda:** \[04:02\] Yeah, a number of times I've seen PRs that have all the import paths changed to fork, and the person being like, "Oh, yeah, you can remove that... I just had to do that to make it work on my machine", and every time it's this little learning process. So hellogopher is actually meant to g...
**Erik St. Martin:** So have you had pretty good success at CloudFlare with that, with people being able to just grab a project and work on it?
**Filippo Valsorda:** Yeah, I definitely shadowed a number of people through the different revisions of hellogopher. It looks like a simple project, it has 110 lines of makefile, but it went through so many changes, even before the Git history. I try to smooth forward and I'm pretty happy that I would help people pick ...
**Brian Ketelsen:** That's nice.
**Erik St. Martin:** Brian, Carlisia, have you guys had a chance to play with it yet?
**Carlisia Thompson:** No.
**Brian Ketelsen:** I've been watching the video on the GitHub repository; actually, I'm watching it again now. It's kind of cool! I'm surprised that you were able to do this so elegantly.
**Carlisia Thompson:** I didn't play with it and I actually didn't know about it until today, and I wish I had, because I helped organize the Gopher meetup in San Diego, and at every meeting there is somebody, at least one person, who doesn't have the GOPATH set up, and I would have been glad to just point them to all ...
**Erik St. Martin:** I feel like every language has that hurdle to get set up when you're not familiar with the environment. I did Ruby for a long time and it never really occurred to me how complicated it is to set up a Ruby development environment...
**Brian Ketelsen:** Oh my gosh!
**Filippo Valsorda:** Yeah...
**Erik St. Martin:** ...until you try to help somebody.
**Brian Ketelsen:** I had to build a whole Linux LiveCD for that.
**Erik St. Martin:** Like, how many steps there are... You have to start explaining Bundler, and rbenv, or what was the other one...?
**Brian Ketelsen:** RVM?
**Erik St. Martin:** Yeah, RVM, and now they have like a Ruby Build one where it kind of builds tools on your path, too... But still, it gets confusing having to remember all these things and set them up. Now we have GOPATH and we have vendoring, and you're downloading projects with the vendor stuff, so yeah... It gets...
**Carlisia Thompson:** But with 1.8 we're not gonna have this problem anymore, right? This is all gonna go away...?
**Brian Ketelsen:** This particular problem won't go away, no.
**Carlisia Thompson:** If you're setting that up the first time, unless you want in a specific place.
**Brian Ketelsen:** You're still gonna have a GOPATH, it will just be automatically set for you if you haven't set it. So we'll still have the confusion that new developers get when they still don't understand what a GOPATH is and why they need to use it.
**Filippo Valsorda:** Yeah, the default GOPATH solves one problem, and it's that now you can just write "go get" and that is enough as instructions to install something, probably, most of the times. But it's definitely not enough for anyone that just wants to Git clone and it's not enough for someone that wants to cont...
**Brian Ketelsen:** Do you require any special project organization, or will this work with any project structure?
**Filippo Valsorda:** \[0:07:49.07\] The point of the hellogopher is also to avoid that Ruby-a-hundred-different-tools scenario is that it works drop-in on normal, go-gettable projects. It's not a different build tool, it's just something that wraps things and does horrible black magic with symlinks that you shouldn't ...
**Brian Ketelsen:** Nice.
**Erik St. Martin:** Now, this is agnostic too, what you use for your vendoring tool, right?
**Filippo Valsorda:** Correct, you can vendor with whatever you want. A few tools will freak out if you're not in the GOPATH, which is kind of legitimate, because vendoring doesn't even turn on outside GOPATH, but if you can get them to actually do their job and vendor stuff, any tool that you use for vendoring will do...
**Brian Ketelsen:** Nice.
**Erik St. Martin:** You actually work on all kinds of cool stuff... I've been following you for a long time because of all the security stuff you do. One of my favorite things you did was the whoami SSH server. I still love this...
**Brian Ketelsen:** It's creepy!
**Erik St. Martin:** Yeah, you can understand how SSH works and how keys are exchanged, but it doesn't really connect at how you could leverage that. Actually, for anybody who's not familiar with it, do an SSH to whoami.filippo.io. It's a lot of fun. Do you wanna tell everybody what it is and explain...?
**Filippo Valsorda:** I should tail the logs and say hi back to people but that would be even more creepy. \[laughter\] So yeah, whoami is this little demo that came out because my flatmate - who deserves a lot of the credit - had dumped all the public SSH keys of GitHub... You might not realize, but if you go to githu...
At the same time I was studying the SSH protocol and trying to figure out a bit of the internals and such, and I realized that the default behavior is just to send preemptively the public keys you're willing to use, then the server responds, "Oh, yes, I like this one." If the server responds that, then you make a signa...
But if the server refuses them all, it will still see them all... And I built this little tool with the golang.org/x/sshpackage that would ask you to use your public keys, refuse them all, but block them, then ask you to do keyboard interactive logging, which is a weird thing that I could just make happen automatically...
**Carlisia Thompson:** So I ran it on my machine and it didn't find my GitHub public key. I'm wondering if it's because I have multiple ones and you grabbed one that wasn't active...
**Erik St. Martin:** \[11:46\] No... The way the SSH protocol works is when you do public key authentication is it will pass all of your public keys, so anything that's in your .SSH directory, you'll see the IDE\_RSA.pubs and things like that... It will pass that, which contains your email address in it.