text
stringlengths
0
1.82k
**Erik St. Martin:** I'm trying to think of who's specifically working on that functionality... Do you remember, Brian, who the specific team was working on the SSA stuff?
**Brian Ketelsen:** I don't know the whole list of team, no.
**Erik St. Martin:** We'll look that up and then we'll put it in the show notes.
**Brian Ketelsen:** So other big news this week, the context package is now going to be in standard library. This is huge, huge. I'm so excited about it.
**Sarah Adams:** Yeah, I'm really excited.
**Brian Ketelsen:** And the way that they've engineered it is really nice too, so that if you're using 1.7, it will use the one in standard library, and if you're not using 1.7, it will continue to use the one in the Net package. That's really awesome.
**Erik St. Martin:** Yeah, that's fantastic. Because gRPC and all that stuff depends on the context package, and we've been using that for -- I don't even know how long that's been floating around. I'm really glad to see it kind of pulled in. Sarah, were you saying something about the context package?
**Sarah Adams:** No, I'm just excited for it to be in the standard library, just a cool addition.
**Erik St. Martin:** And hopefully a lot more people will start using it as part of their packages where they expose network requests and things like that, because that's really the power in it - having the context forwarded along, so that you can stop it anywhere in the process.
**Brian Ketelsen:** Yeah, so all you library developers out there, if you're not putting context as the first parameter of your public functions, now is a great time to start doing that, please. I wanted to say please, I don't wanna sound too bossy. I can come across that way sometimes.
**Carlisia Thompson:** And from the little experience that I have with Go, I see a lot of times when people use other network packages just so they can get the context, and I would even do that, because I don't wanna do that stuff by hand. But now that it's in the standard library, I wonder how it's going to impact the...
**Erik St. Martin:** But is it really a competition, though? I think at the end of the day it's about writing good quality software, that's readable, and I think that by having external libraries that people really like - and we kind of get consensus on these patterns - I think it's okay to pull that stuff in. Because ...
**Brian Ketelsen:** It'll certainly be easier to use.
**Sarah Adams:** Yeah, I wonder how the Gorilla toolkit is gonna change because of this, because they've implemented their own network context, I think. I haven't used it in a while...
**Brian Ketelsen:** Yeah, Gorilla has its own context, and every other mux on the planet has its own context; I'm really excited about them not having their own contexts. I hope that they all converge to use the standard library context.
**Erik St. Martin:** That's actually really interesting, I hadn't even considered that. I mean, I've used the Gorilla mux in the past couple of years, but I don't think I've used anything else from the Gorilla stuff in a while. So that will actually be really interesting to see how that's adapted to this.
**Sarah Adams:** Yeah, and I think the Gorilla mux even imports its own Gorilla context, within the mux package. So it will be interesting to see if they go forward with the Go standard library context.
**Erik St. Martin:** We should email them and ask.
**Brian Ketelsen:** Open an issue on the GitHub repo.
**Erik St. Martin:** Maybe one of their developers is one of the two listeners. \[laughter\] Alright, so one of the other projects that I've been using recently is vendor check. I noticed that they've got an update that now tells you your deprecated dependencies, which is awesome. So basically it goes through your vend...
**Brian Ketelsen:** This is interesting, because we've talked about the blog post that this originated from in our last episode, the CloudFlare blog post about creating the simplest possible SSA tools. Vendor check was an extension of that, and it's nice that it's getting some very usable features; it will be good to g...
**Carlisia Thompson:** It sounds to me almost like vendor check should be side by side with fmt.
**Sarah Adams:** Yeah, and go imports.
**Brian Ketelsen:** Yeah, it's definitely a must-have tool.
**Erik St. Martin:** Yeah, and I think that the vendor stuff is probably early for that stuff to kind of get pulled in, at least adopted by the Go team, right? Because it's only been recently that there's been this agreement that maybe the Go tooling should handle vendoring more, so it will be interesting to see how mu...
**Carlisia Thompson:** Exactly.
**Erik St. Martin:** Like, there's a Go meta-linter and stuff like that that runs all the suite of different tooling.
**Carlisia Thompson:** I can totally see that happening, too.
**Brian Ketelsen:** So on that note, on the idea of having vendor tooling being built into Go itself, I know that Andrew Gerrand was talking about sponsoring a talk or a panel discussion on the hack day at GopherCon on the 13th of July, for an hour or so, talking about packaging and vendoring. So if you're got strong o...
**Erik St. Martin:** And strong opinions in general. I know that they're wanting to do kind of a collaborative session with big Go users and kind of seeing what pain points are there and how people feel that the Go team can ease those pains, and make it easier to adopt and use Go.
**Carlisia Thompson:** And on that topic, there is an issue opened on the Go repo where they just pull in everybody's opinion into one place - at least they put links to things, and there's probably something good to read through if you are going to go to this event and discuss, so we have all the information...
**Brian Ketelsen:** It's a really long issue.
**Carlisia Thompson:** Yeah, it's huge. But it's not the Go team endorsing any way or another; it's just gathering everybody's opinion in one place, and giving it as it is - "Okay, this is what people are saying. Let's just have it here, so we're not replicating this all over the place, so we have a starting point. We ...
**Erik St. Martin:** I ought to pull that up when I have a weekend.
**Brian Ketelsen:** It's longer than a weekend.
**Erik St. Martin:** I can only imagine.
**Carlisia Thompson:** Yeah. It's not light really, it's very thoughtful expressions of how things could be done technically. I'll find the link.
**Erik St. Martin:** Awesome. So on a sad news side of things, did anybody see the email that Rob Miller sent out to the Heka mailing list?
**Brian Ketelsen:** I did.
**Carlisia Thompson:** No, what?
**Brian Ketelsen:** Very, very sad.
**Erik St. Martin:** Yeah. So Rob Miller works for Mozilla on a tool called Heka. How would you best describe Heka, Brian?
**Brian Ketelsen:** Heka is a stream processing tool that you can use to take inputs and process them and munge them and do strange things with them and send them back out to other places. One of the most common use cases would be log aggregating and management; it's significantly more complicated than that, but that's...
**Erik St. Martin:** Yeah, it's basically like a pipeline, and there's different inputs you can swap out - collectors and emitters and things like that, so you can take inputs from various different types of systems, and you can output to various types of systems. There was a really interesting project, and he presente...
**Brian Ketelsen:** Discontinued Mozilla support perhaps, or Mozilla sponsorship.
**Erik St. Martin:** ...and I think that they're open to somebody else taking over the project, but they don't have the time to help facilitate that takeover either, and I think he expressed some concerns about even the patterns it was designed under; the way they were using channels wasn't quite hitting the performanc...
**Brian Ketelsen:** That'd be a great idea. We'll link to the mail list announcement in our show notes. It's way too long to discuss here, but the main takeaway from the email that he sent out was that the refactoring required to make Heka perform significantly better than it does now, which is actually really solid pe...
**Carlisia Thompson:** That would be an amazing topic, I'm sure a lot of people can benefit. I can benefit from it.
**Erik St. Martin:** So before we get into some discussions about all the things that Sarah is doing these days, we typically go through some interesting Go projects, because Brian is full of -- just this encyclopedia of projects. But before we go into that, we don't need Brian anymore. Have you guys seen the LibHunt t...
**Carlisia Thompson:** No.