text
stringlengths
0
1.49k
**Brian Ketelsen:** I played with it just a couple weeks ago and I had a blast. I did things that were completely not SSH with it, which I think was the best part.
**Jeff Lindsay:** Yes... Yes! I do that all the time. I love doing non-SSH stuff with SSH. It's a great protocol; it's this whole layered approach... It has authentication stuff, and that's all pluggable, and then it has a connection layer where you can kind of tunnel multiple connections, and then it gets into specifi...
It actually looks a lot like HTTP/2. It has a lot of the same primitives in terms of like -- you know, instead of TLS, it has its own security authentication encryption mechanism, and then the streams in HTTP/2 map to the connections streams that SSH has...
I was using it for all kinds of crazy stuff. It's a really great protocol. And then of course it all works with SSH keys, which everybody is pretty comfortable with, so...
**Erik St. Martin:** We hope...
**Jeff Lindsay:** I actually rewrote localtunnel using a library that I built on top of the SSH stuff, and it turned localtunnel into like a hundred-line program. So to me that's always an achievement, when I can build a non-specialized library that allows maybe something I made before that was very complicated to be r...
**Erik St. Martin:** Yeah, deleting code is always awesome, and I love when people create things that are beyond what I thought. You built this really hyper-focused, specialized thing, and then somebody comes along and builds some kind of abstraction that takes away 90% of your complex code, and you're like "Wow, I did...
**Jeff Lindsay:** \[48:19\] And in Go, that usually happens when you're using interfaces, because having interfaces for stuff is really great. I was just saying the other day that the [Afero](https://github.com/spf13/afero) file system project - that should be in the standard library. There should be an abstraction for...
A lot of pieces could be removed from that if you just replace the file system that Hugo works with with the file system that talks directly to GitHub... So building a file system implementation that actually is a GitHub repository, using the GitHub API. And that way you can write that and you could almost literally dr...
**Erik St. Martin:** I wonder if \[unintelligible 00:50:05.15\] would be like using Fuse...
**Jeff Lindsay:** Yeah... Stuff like [Fuse](https://github.com/libfuse/libfuse) is really cool. It all depends on the requirements that you have. Fuse requires kernel extensions. I can tell you about something -- kind of an alternative to Fuse is using [9P](https://en.wikipedia.org/wiki/9P_(protocol)), which is kind of...
The cool thing about 9P is that it already is in the Linux kernel. You can just mount directly -- you don't have to install anything extra, you can just, in most cases, mount a 9P file system. This is how you can do custom file systems without having to do Fuse and run an extra daemon, and have a kernel extension insta...
\[51:34\] There's a really great 9P protocol project that one of the guys at Docker made, and it was missing an actual server implementation, so I wrote that... And I actually ran -- Jonathan from Flynn was actually thinking exactly the same thing... "Oh, you can use this as a better way to deploy your current director...
So he was thinking the same thing and found the same library, and we actually worked -- it's been a while since we... We catch up every now and then, but then we got to kind of collaborate on a little bit of code fixes to this.
So yeah, using SSH you can then tunnel that 9P connection through it, so that's how command.io is going to expose your local directory to the container on the remote side in the cloud, using 9P. So Fuse is really cool, but 9P is also really cool, especially because it doesn't require extra stuff.
**Brian Ketelsen:** That's crazy awesome. I just read an article that I think I found on Hacker News maybe a week or so ago, on building your own 9P service, and it was one of the best-written articles I've ever read. I know I tweeted it... I have to come up with the link to that. It was a really good article.
**Jeff Lindsay:** Yeah, I'd like to see that. It is a really simple protocol, it gets the job done, it's pretty simple to understand, and this library that I found, it was implemented beautifully. It's like "Here's an interface that maps to the protocol's interface in Go." There's a Go interface for it, so it's very ea...
I'm always frustrated when there isn't an interface, and I wanted to wrap something. I'm like, "Oh, I could fix this if I could wrap it", but if I wrap it, it's a different type, whereas if it was an interface, I could make my own implementation that wraps the existing implementation and changes it, and it would still ...
**Erik St. Martin:** Yeah, I think it's hard too to figure out when the correct time for that is, right? Because you have the other side of it too, where you make everything return an interface, and your interfaces aren't really figured out yet, when you're that early in writing code... And then if you're always moving...
**Jeff Lindsay:** Yeah, and so that's why I wish more interfaces were in the standard library, like the file system interface that the Afero project does. It's basically -- the Go developer is helping you design your interfaces; it's like "Oh, you don't have to think about how you would do io stuff, we've already come ...
That's where it's hard... Designing API's is hard; it takes a long time to understand that domain well enough to be able to create the simplest API for it, that is expressive and lets you do everything that you need to do, but is also very simple. Most developers don't have that luxury, unfortunately.
I have a lot of time in the sense that like, if I have enough money, I can spend a lot of time on something, but even then I'm like "It's taking me a long time..." It takes a long time to get good API designs. Maybe stuff like the Go Commons project is a great place that we can experiment, that current conversation abo...
**Brian Ketelsen:** \[56:12\] Yeah, that was one of my most exciting things about the Go Commons idea, which was everything should start with an interface, and the implementation should be second. Everything should have an interface.
**Jeff Lindsay:** Yes... Yeah, that'll be exciting. Standard com is kind of like that, and I'm developing a lot of interfaces for the hooks. The neat thing about the components in com is because -- so I have this kind of hypothesis when you're writing reusable software that, you know, your ideal is that it's simple, bo...
If you introduce hooks and extensions, whether it's callbacks or whatever, you're able to allow it to express a lot more things and let it do more things than if it didn't have those. So that actually reduces the amount of code that you need, because a lot of times you can say "Oh well, this is relatively common, but n...
So I don't know, this is part theory, but I've been really enjoying building applications in this paradigm, and it's all thanks to interfaces.
**Brian Ketelsen:** Yeah, interfaces are like the be-all-end-all of Go, for sure. Well, I think we've talked so much that we are pushing our luck in terms of recording time today, so we probably need to move on to \#FreeSoftwareFriday and skip the news this week, because I've know we've got a hard recording stop in jus...
**Erik St. Martin:** I'll kick mine off...
**Brian Ketelsen:** Alright.
**Erik St. Martin:** So I didn't do a lot of development this week. Well, a little bit... So I've been in New York City at this Open Hack thing that Microsoft's been hosting, which is like a cool little hacking challenge conference, and I'll write up something, a little bit more about that, but it's been super fun. As ...
So literally, to get our service monitored by [Prometheus](https://prometheus.io/) in our [Grafana](https://grafana.com/) graphs sidecar process that scraped this stuff over a custom protocol, use the Go library, which automatically gives you an HTTP listener for Prometheus with a slash metrics endpoints to expose the ...
\[01:00:18.27\] That's so useful, not having to custom-configure Prometheus every time you launch a new app, and then reload the configuration for Prometheus, and stuff... I just thought that was really cool.
**Brian Ketelsen:** That's impressive.
**Jeff Lindsay:** It's the future, I love it.
**Erik St. Martin:** It's ridiculously cool.
**Brian Ketelsen:** You know, when I was a kid, we used to have to write our own Kubernetes configurations for everything...
**Erik St. Martin:** Yeah, that was exactly my thought; I was like, "Wait, whaaat?"
**Brian Ketelsen:** In the YAML, with no parser. Uphill both ways. Alright, well I'll go next for \#FreeSoftwareFriday. This is kind of cheesy, so you'll have to forgive me, but I wanna call out Progrium Envy on GitHub, because it inspired me to do a million things that I never would have thought of. I'll throw it in t...
**Jeff Lindsay:** Wow, yeah. That's really cool.
**Carlisia Thompson:** Okay, I guess it's my turn. I am going to give a shoutout to the [Google Working Group GreaterCommons](https://greatercommons.com/cwg)... It is a really long-winded name, but it's a selection of courses about Go, and they are free, and I guess they are curated by Google or done by Google, I'm not...
**Jeff Lindsay:** That's awesome.
**Carlisia Thompson:** Yeah, it's a great resource because it's free and supposedly curated... So I'm looking forward to seeing people using this and see what feedback we get, and getting more courses in there. I know Todd - I cannot pronounce his last name... Somebody help me. You know [Todd](https://twitter.com/Todd_...
**Erik St. Martin:** McLeod?
**Carlisia Thompson:** Yes. I know some of the courses are his, and he has such good feedback on his courses; everybody loves his courses. So definitely, if you're looking to learn Go, you should check it out.
**Brian Ketelsen:** Awesome. Todd's got so much energy... He's fun to watch.
**Carlisia Thompson:** Yeah, he's a good person.
**Brian Ketelsen:** Jeff, is there any open source project you wanted to give a shoutout to, or a person, or...?
**Jeff Lindsay:** I've been trying to figure this out for a long time, since I saw the notes... I was like, "Oh, I'm gonna have to pick one or two..." Like, even just two is hard. I don't know... Just because I touch it so much, most of the stuff that -- I forgot his real name, but spf13. He did Viper, and...
**Erik St. Martin:** [Steve Francia](https://twitter.com/spf13), yeah.
**Brian Ketelsen:** Steve Francia.