text
stringlengths
0
1.49k
**Erik St. Martin:** I missed it by two minutes. I was like, "Here we go!"
**Brian Ketelsen:** We didn't do too bad with timing, though.
**Erik St. Martin:** Yeah, I was actually looking at my timer... I must have started it two minutes after the hour... But yeah, that was kind of funny. He's accusing me of having my brother on the Twitter account. \[laughs\]
**Brian Ketelsen:** It's probably true. Very few people would know the difference.
**Erik St. Martin:** No... Even at the conference, very few people know the difference.
**Travis Jeffery:** Actually, I'm curious... How many of you use a Go framework for the web rather than just using the standard library?
**Erik St. Martin:** It depends on what I'm doing. Brian's been doing a lot more framework and code generation stuff than me. Recently, I've been writing a lot of outbound service type stuff, so I haven't really had the need for a framework. The two components I've mostly been working on recently are just interacting w...
**Brian Ketelsen:** From my perspective, I've done everything from pure NET HTTP all the way up to Revel when I first started Go, and everything in between. For me, I was always looking for that Rails experience without the Rails magic, and Go Buffalo has absolutely brought it back to me, so I'm super excited about Buf...
The new Gopher Academy website is written in Buffalo, the new GopherCon website is written in Buffalo, and I've done a couple others, too. It's so fast, and it's getting better every day.
**Travis Jeffery:** Yeah, that sounds good. I'll have to check it out. I've always just been like a standard lib guy; the Gorilla libs are really awesome. Basically, I would just tag those on as I needed, or whatever else.
**Erik St. Martin:** I like standard lib, but there reaches a point too where there's so many endpoints... If you're building out a full admin interface where there's just a lot of endpoints, that feels like it could get repetitive and there'd be some shared logic for authentication and authorization... Some of that st...
**Brian Ketelsen:** I was gonna say, that's because I'm writing all the APIs and web stuff, Kubernetes boy.
**Erik St. Martin:** \[laughs\] I don't know... Mine has its pain, too.
**Brian Ketelsen:** Oh, absolutely.
**Erik St. Martin:** Did you not hear that I have to man-in-the-middle Docker?
**Brian Ketelsen:** I did catch that and I feel your pain, that sounds terrible.
**Erik St. Martin:** It was kind of fun. The paining part is where it upgrades the socket. I was like, "Sweet, I can just the HTTP reverse proxy and just give it some socket knowledge." That didn't work at all, because it upgrades where basically they start talking just straight TCP and no more HTTP to each other for s...
**Brian Ketelsen:** I'd like to see that code, because not too long ago I was doing Docker-backed web terminals, and I got stuck with that same websocket upgrade, because I was trying to connect the STDIN and STDOUT from the web terminal directly to a Docker container running a shell, and there's that point in the midd...
**Erik St. Martin:** \[56:11\] Yeah... It's actually kind of cool, because you can just basically pipe the two connections together. But yeah, I'll help you through it.
**Brian Ketelsen:** I'll buy you a beer.
**Erik St. Martin:** Apparently I owe Brian Downes a beer, too. Remember when we joked about if somebody cosplayed as Bill Kennedy with a hat, or something?
**Brian Ketelsen:** That's right!
**Erik St. Martin:** ...and I never saw this picture - he is dressed clearly with a Bill Kennedy hat and a Dave Cheney beard, and I missed it.
**Brian Ketelsen:** Say it isn't so!
**Erik St. Martin:** So I owe somebody some beer. Hopefully, they will be at the next GopherCon.
**Brian Ketelsen:** That is awesome.
**Erik St. Martin:** Maybe we'll invite him to the dinner.
**Brian Ketelsen:** That's a good idea.
**Erik St. Martin:** So we have a tradition, too... It's a little late now, but most people don't know this - every year, Brian and I take whoever the first ticket purchaser is for GopherCon out to a really nice dinner. So next year you want that to be you.
**Brian Ketelsen:** Yeah, that's been really fun. We have people that camp on the ticket buying page just to get the honor.
**Erik St. Martin:** It's fun. Alright... Anybody have anything else before we close out the show and move after show? Even though we're kind of in the after show...
**Brian Ketelsen:** Yeah, when Carlisia left, everything got informal. \[laughter\]
**Travis Jeffery:** Do you guys wanna talk about this Golang dev discussion about the standard logging interface?
**Brian Ketelsen:** You mean the one I started?
**Travis Jeffery:** Yeah, I guess you started -- well, someone else started it, but they started it because they saw your tweet.
**Brian Ketelsen:** Yeah, Peter started it because of my tweet. So I suggested on Twitter a couple days ago that it would be nice if we had a single interface for logging.
**Travis Jeffery:** Yes... Yes!!!
**Brian Ketelsen:** Well, the biggest mistakes I see in Go - and there aren't that many, to be honest; Go is a very well-written language... But I think it's a mistake that the logging package is a concrete implementation and not an interface.
**Travis Jeffery:** Yes, it would be so awesome... Because everyone has their own login implementation, and it just becomes a mess...
**Brian Ketelsen:** Yeah, it's insanity.
**Travis Jeffery:** I love it.
**Brian Ketelsen:** So regardless of whether you think that library should be logging - and that's its own discussion - many Go libraries do log, and anything that touches Kubernetes, any of those clients, they use glog (Google's logger) and it's insanity when you've got all of these different libraries mixed together....
**Erik St. Martin:** Well, I mean you can set where you logarator is using a global, too.
**Brian Ketelsen:** Only if they're not using something crazy...
**Erik St. Martin:** Right, yeah.
**Brian Ketelsen:** There are log packages that don't allow you to override the log output, and that's been really frustrating. I forked one of them once - I don't even remember which it was - just to add the ability to get to the logger, so you could change its output to the standard logger. It's ridiculous.
So I suggested on Twitter that we needed to have a standard interface for logging packages, and obviously, the reason that we have all of this logging package stuff is because Go's logging implementation doesn't have log levels and it doesn't have structured logging. I think pretty much everybody will agree at least wi...
An interface that covers log levels and structured logging, in the standard library (which is my biggest argument) - if it's not in the standard library, you're wasting your time - it would allow us to plugin whatever logging library we liked, whether it's Logrus or Log15, or Go kits, or whatever, and they would all ju...
**Travis Jeffery:** \[01:00:11.04\] Yup, it'd be awesome.
**Brian Ketelsen:** Java's had it for years, Log4j.