Go is epic at Epic! Chat with Creed Haymond about Go in gaming
The show is supported by you. Stick around until after the news to hear some more about that. This is Cup o' Go for Friday, 04/03/2026. Keep up to date with the important happenings in the Go community in about twenty minutes per week. I'm Jonathan Hall.
Creed Haymond:And I'm Creed Haymond. Creed?
Jonathan Hall:Where's Shay? Oh, I forgot Shay is on vacation right now. Welcome, Creed. Hello. Thanks for joining today.
Jonathan Hall:Why don't you tell the audience a little bit about who you are since I don't think they know your voice?
Creed Haymond:Yeah. I'm Creed Haymond. I've been a lurker in the community for too long. It's time to put a voice now to my name. But yeah.
Creed Haymond:Cool.
Jonathan Hall:And where do you work?
Creed Haymond:I work at Epic Games.
Jonathan Hall:Woah. And do you use Go at Epic?
Creed Haymond:Starting to. There are teams that actually have historically been using Go, but our team is now beginning to adopt it.
Jonathan Hall:Very cool. We'll talk about that a little bit more. So stick around. You're gonna wanna hear about how they use Go with Epic. But first, some news.
Jonathan Hall:Why don't you kick it off, Creed, with this announcement?
Creed Haymond:Yeah. First announcement is there is an upcoming security release for Go one dot 26 dot two and Go one dot 25 dot nine. This is pre announcements coming out on Tuesday, April 7, and it should be fixing eight CVEs. Let me just read those codes for you.
Jonathan Hall:Yes. And memorize it. Well, it will be on the test later.
Creed Haymond:Yep. Yep. Yep.
Jonathan Hall:Alright. So stick around next Tuesday. You'll want to keep your eyes out for the new version of Go and upgrade to avoid eight potentially serious security problems. Also this week, Go team published a new blog post. This one from Mark Freeman called type construction and cycle detection.
Jonathan Hall:Creed, how much do you deal with Go types?
Creed Haymond:I'm pretty sure when writing Go a 100% of the time.
Jonathan Hall:Yes. Yes. So we all use Go types, but you probably haven't thought about them as much as this blog post details. It talks specifically about how types are constructed when parsing a Go program during the compilation. Walk through some simple examples.
Jonathan Hall:Let's say you have type t that is a slice of type u, and then you have type u that is a pointer to int. It just sort of goes through like what what steps does the compilation process go through to construct these types? And then it goes into some more complex examples, you know, circular types, you know, where something a type refers to itself. And there's there's not really like a a main takeaway from this, except by by reading it, you'll know more about how types work and go and how they're constructed. The reason this came out recently was because they made some improvements in Go 1.26 to how types are handled internally.
Jonathan Hall:It should not affect how you use Go, so you don't need to worry about this if you don't want to. But it makes it a little bit more, I think, efficient and just sort of cleans up some corner cases. And they mentioned, without being very specific here, that this is setting us up for some future improvements in Go. So don't know what that means. I hope it means union types, but we don't know.
Jonathan Hall:Yes.
Creed Haymond:I think it's really just it's all about, you know, the new Go TypeScript compiler. They wanted to compete and be able to describe more types.
Jonathan Hall:That's gotta be it. That's gotta be it. So anyway, it is a good read, especially if you're into sort of nerdy stuff about how your language works under the hood. But it's not gonna fundamentally change how you write Go. So it's up to you whether you wanna go read that one.
Creed Haymond:Very cool. Next up is there's a cool blog post by, what is it, packagemain.tech. Alex, I'm gonna butcher your name. Be out to describing building a Whales application using desktop app building experience, but you can build it in go and front end framework of your choice. Really kind of cool.
Creed Haymond:Just describes building this application.
Jonathan Hall:Isn't Wales kind of like Electron written in Go? Or am I confusing myself?
Creed Haymond:It's somewhat like that. I think the there's also a Rust one like Tauri or something.
Jonathan Hall:Okay.
Creed Haymond:I think the idea is that instead of booting up a full electron app or or mini browser or something to consume all the available expensive memory on your machine, it it just uses like a web view or web kit or something I I think most operating systems have that available to to load up a web view. Whales specifically will generate a little bit of like JS bindings. So it's almost like a little RPC, and you can code, you know, most of your logic if if you are writing it that way in Go, and then have it bound to little functions you can call and rendering your application on the front end.
Jonathan Hall:Okay. So that that's what Wales is for those who didn't know like me. But now that's not the point of this post. This post is something specific in Wales. Sorry to interrupt.
Jonathan Hall:Continue, please.
Creed Haymond:Oh, that's okay. And and a lot of it, I think, was about that, but it actually kinda goes through building the like a two factor auth application and goes a little bit into how it works, some of the bytes and some issuing of of certs and stuff. It's it's a pretty
Jonathan Hall:cool little
Creed Haymond:post digestible. And I think yeah. Links to the source code as well. So, yeah. Might be a little if you're interested in building desktop applications or two factor, take a look.
Jonathan Hall:Nice. Thanks, Alex, for the for the post. It just came out a couple weeks ago, so it's pretty timely. Next up, I found a little post over on dev.2 called Native Chaos Engineering Testing Resilience with Fault and Latency Injection. So you've probably heard of Chaos Monkey.
Jonathan Hall:I think Netflix invented this thing. Right? It's like the idea is monkeys running around your data center and plugging cables and like, can your can your system withstand that?
Creed Haymond:I call that my kids. Yes.
Jonathan Hall:Yeah. Definitely. So anyway, the whole the whole Chaos Monkey is is part of the larger sort of methodology, if you will, or or or whatever about chaos engineering, the idea of intentionally breaking things to prove that your system can can keep working when things break. And so this blog post goes into doing some of that natively in your Go code. So it's about how to a little configuration file here to configure how frequently and how randomly things break on your on your system, putting in circuit breakers, so stuff like that.
Jonathan Hall:So it's not a it's not a long, super detailed one, but if you're new to this concept and you want to or or new to doing it in Go, this is probably good post for you. My chaos engineering usually is limited to running on preemptible containers. Because it saves me money too.
Creed Haymond:That's a good idea. Is this something that you write, you add to your application, you know, wrapping HTTP clients so it's like simulating, hey, network disconnecting,
Jonathan Hall:stuff like It's specifically about doing a a chaos injector middleware. So I think this would be limited to, like, maybe a web application. But so it's not gonna be as robust as something that runs external to your application, but, you know, it's a good start to doing something, you know, some chaos engineering in a in a web application.
Creed Haymond:That's really cool. Alright. And then we have this GPDF, a pure go zero dependency PDF generation library.
Jonathan Hall:Why do I need another PDF generator?
Creed Haymond:And you know what? It's the coolest format. Don't know why know, yeah. I mean, like, I'm sure AIs love it, you know, way better than markdown slash sarcasm slash, I don't know. Put my hands up like, oh, maybe you've got a cool resume and you wanna build it with purely go, you know, all the way down.
Creed Haymond:But, yeah, I mean, kinda cool. What makes it different? Standard library only. It also has an awesome landing page. So it's run-in design whether or not the dev did this themselves.
Creed Haymond:We got a little help from AI. Hey, it looks great. Up here go zero dependency PDF generation library. First class first class CJK support. Don't know what that is.
Creed Haymond:And declarative 12 column grid design. Cool. And they there's even some really good docs and a little GUI editor built right into the site for building PDFs. Nice.
Jonathan Hall:The thing that jumps out at me is the benchmark results. I'm always a little bit skeptical when I see someone's own benchmarks, right? Like, what was the test case? Only PDF library I recall using in Go was GoPDF, and this claims to be 10 times faster. Wow.
Jonathan Hall:And they also mentioned a couple others. GoFPDF or GoFPDF, I don't know how that's pronounced, and Maroto. I don't know what that is either. But of the four, GPDF is by far the fastest. So if you need fast PDF generation in Go, I think this is one we can check out too.
Creed Haymond:I'm curious what the use case of like really fast p I guess like if if you're a company, you're generating reports on demand. I've had to wait before, you know, you click the get me a PDF.
Jonathan Hall:Especially if you're doing them in bulk. You know, know, these are, thousands or hundreds of thousands every every month or something. You might want that to run faster. So
Creed Haymond:Yeah. Yeah.
Jonathan Hall:Yeah. Alright.
Creed Haymond:Very cool.
Jonathan Hall:I'll check that out next time. Need to make PDFs in Go. We have breezed through the news this week, but I think that's okay because I hope we're gonna have a very interesting conversation about Go and Epic after the break. We do have a couple of lightning round items and a quick break before we jump into that though. Creed, will you stick around to talk about that?
Creed Haymond:Absolutely.
Jonathan Hall:Awesome. Thanks for listening to Cup o' Go this week. As always, we're sponsored by you, our listener. If you're not already a Patreon, we'd love to have you join. It can be either free or a small amount of money.
Jonathan Hall:I don't remember the number. Is it $3 a month or 4 or 8 or something like that? I don't know. Cup o' Go. Dev.
Jonathan Hall:I should just pop it up, and I could look at it myself.
Creed Haymond:200.
Jonathan Hall:200? 200. That also works? Yeah. Yeah.
Jonathan Hall:Yeah. We have 61 Patreons right now. You could be number 62 or 63 or lucky 64. We love those powers of two on this show. You can also support the show non financially just by telling a friend or colleague about the show, leaving a rating wherever you listen to your your podcasts.
Jonathan Hall:And we also have some fun swag. If you'd like a t shirt or coffee cup, that kind of helps the show. Like, it's mostly subsidized, but, like, technically, we might get a few cents off of each sale. Let's see. I think the only other thing I wanna mention in the lightning round is I personally I guess I'm sponsoring the show now.
Jonathan Hall:I am looking for new clients. I have a I had a contract wrap up. We we'll be wrapping up next week. So if you are looking for some part time Go help, check out boldigo.tech/subscription where you can see how I do a non hourly subscription. I don't like to charge per hour because I think it's bad for the client and for me, bad for everybody.
Jonathan Hall:So I do a kind of unique way to sell my services. Check it out. Boldigo.tech/subscription. I think that's it for our break. I want to talk to Creed about what he does with Go.
Jonathan Hall:First, a quick lightning round, and then we'll jump into the conversation.
Creed Haymond:Lightning round.
Jonathan Hall:Alright. First in this week's lightning round, I am announcing a fork that I have made. Now I'm kind of reluctant to to to announce this because I've only been using it personally, testing it, but I have forked Golang CI Lint, and I really, really don't want to, like, be competing with Golang CI Lint. I think it's a great product. I'm going to keep using it, and I'm expressly forking it to add a very specific characteristic to my fork.
Jonathan Hall:So I don't want anybody to think that I'm trying to, like, steal the ideas or anything from there, But go for lint, github.com/flimzy, that's with a z, flimzy, slash goforlint is a fork of Golang c I lint that only adds bug fixes between major Go releases. The the the purpose of this is I was tired of my my linter breaking every three months or so when new new great features are added to Golang c lint, but I don't necessarily want the new features. I just want the bug fixes. So that's what I'm doing. Whenever Golang c I lint releases a new a new patch, I cherry pick the bug fixes, include that, and that's all I do.
Jonathan Hall:Or Claude does that for me. Whatever. So if you're interested, if if you have the same sort of concern about your lint or breaking between Go releases that I did. You can check it out. Go for Lint.
Jonathan Hall:Right now, it's a version one point twenty six point two. Basically, the one in the 26 matched the Go one and twenty six. The point two was unrelated. That just happens to be how many iterations I've made. But 1.26 x will be stable.
Jonathan Hall:No breaking changes until one twenty seven comes out, then I'll tag one twenty seven. That's it. That that's that's my lightning round item.
Creed Haymond:Very cool. Well, I have one kind of just a sort of a shout out to a great library that I was using recently, the Valvky Go. It's Redis Valvky. If you're interfacing with Redis or Valvky, it's a great client implementation. Specifically, they have this feature auto pipelining.
Creed Haymond:So any, like, item potent, so like gets and such, it can actually kinda like behind the scenes batch them all together and and send them as a pipeline operation to Redis and get all those operations back in the same thing. This is great for high throughput stuff as long as you're not worried about, like, head of line blocking or some other problem because, you know, if, like, one operation is taking a little longer than all of them in that batch kinda get impacted. But but, yeah, great library, good docs. I don't know. It was just something I found that was very surprisingly efficient and easy to use for my use case.
Jonathan Hall:So is this a library you would use when you're storing your millions of PDFs that you've just generated?
Creed Haymond:Exactly. Precisely. You know?
Jonathan Hall:Nice. Where are
Creed Haymond:you gonna put all those PDFs?
Jonathan Hall:You gotta put So them remind me, is is Valky like a fork of Redis, or is it a completely new product? I don't I don't I know that Redis, like, did this controversial we're not open source thing anymore a while back or something, That's And that's where this came from. What what tell me this this horse history there just briefly.
Creed Haymond:Yeah. Now, I'm I might get it kinda wrong, but
Jonathan Hall:like Don't hold from me to it.
Creed Haymond:Yeah. These are my opinions, not they don't reflect anything from. Yeah. When Redis changed their licensing, Valvassori, I believe it it came purely from Amazon, but it was like a an official open source fork of Redis at the time. I think what happened too is, like, Amazon's interest in hosting Valvky became that they they could, like, fork it and then not pay the licensing or whatever that Redis was going to cause to them.
Creed Haymond:So they gave discounts to folks to move over to it. But it was a fork. It has diverged since Okay. It's forking. So like now they're kinda like supporting slightly different feature sets from what I understand.
Creed Haymond:But like the core I mean, you're just looking for a cache, I'm sure you could swap one for the other at any time. And I from what I understand, I think Redis has now also maybe walked back some of their licensing. I can't I can't quite remember.
Jonathan Hall:Yeah. I I can't follow that either. I know some some of the big players have changed licensing and changed back and I don't remember if it's one of them or not. Okay.
Creed Haymond:Oh, yeah. Elasticsearch was the other one. Maybe I'm mixing this. I could be crossing the two stories because the same thing happened with Amazon and OpenSearch. And HashiCorp did
Jonathan Hall:did similar stuff too at some point.
Creed Haymond:Oh, that that's right.
Jonathan Hall:Terraform and and other things. Yep. Alright. Let's end the news segment here. I wanna talk about games.
Jonathan Hall:I don't I I don't know if you write the games in Go, but we'll we'll figure that out. That's what's coming up next year. So stick around for a conversation about Go and Epic. Alright. Creed, tell me about, just be a wide open question here.
Jonathan Hall:Tell me about Go and Epic. All all the new games are written in Go now. Right? Is that basically the TLDR?
Creed Haymond:That is right. Yeah. You gotta understand Fortnite is now 80% Go. No. I'm just kidding.
Creed Haymond:I'm total joke, which by the way, should just just a quick note, these are my personal opinions. Anything I say or do don't reflect the views of my employer Epic Games. Right.
Jonathan Hall:Right. Understood.
Creed Haymond:There there's my my thing. But yeah, Go at Epic, which is I will speak purely from, like, my my own team and organization perspective, because there are actually some orgs in Epic that have been using Go or historically. But depending on what, you know, org structure you're under, ours, which I I work for Epic Online Services, which is a pretty cool like game developer APIs, essentially that game developers can can add to their code to keep stats, achievements, like all these things that they want. They they can, you know, use these game APIs in their games, and we have an SDK and everything. Well, I help build the web services that power those.
Creed Haymond:And historically, they've been in Aka Scala, which is yeah. Really fun. Aka is like the actor, like a really popular actor framework functional paradigm for, yeah. And big big Java ecosystem built under that. However, Akka, speaking of licensing changes, they changed I I guess, LightBend, I think, as the own Zaka or whatever created it.
Creed Haymond:They changed the license on there and anyway, so there was there was migration work essentially to start rewriting a lot of these services that we have or start porting them into either Peco or Java Spring. And I actually came from Amazon before I worked at Epic Games and also wrote plenty of Java there. So and I look, I'm not a wolf in sheep's clothing, I swear. I'm I'm a gopher.
Jonathan Hall:Alright. Okay. I don't know
Creed Haymond:what that would be a gopher equivalent of of wolf in sheep's clothing, but
Jonathan Hall:Gopher and furry clothing or something? I don't know.
Creed Haymond:Yeah. Exactly. Oh, man. Anyway, that being said, as my team personally, like, we we struggled with this whole starting to rewrite stuff in Java Spring. Struggled in the sense that, like, as we were doing a lot of this work, we kept on running into all these roadblocks.
Creed Haymond:And and to be honest, like, our team, our critical team of like, our core team, I should say, specifically, we all took issue with with the paradigms of Java and Spring. And it just and and Gradle, the build system that we're using to build all this stuff. And it's it's like you have to learn an entire language to build your application. Gradle. That's great for So yeah.
Creed Haymond:And then it it it kinda came down to like actually, about a year ago, I'd heard enough complaints from my teammates. And and I'm not one to like, you know, step in and be like, hey, by the way, this language is better than all your languages and let's just port everything over, you know, just willy nilly. But I'd heard enough that, like, you know, I I approached my team and was like, hey, I don't know how you guys feel like. We we have this opportunity. We're sort of re architecting and rebuilding a few of these systems.
Creed Haymond:We're at this hinge point of, like, we could decide maybe we don't wanna actually use Java Spring. Like, what if we just did that? And and I kind of pitched to them this idea like, hey, you know, some of them are relatively familiar with Go from previous work. And so I I pitched the idea like, hey, look, let's start using this. And and a year ago, I they said, actually, yes, let's let's totally do this and kinda proposed it.
Creed Haymond:And it was summarily shot down by somebody else who kinda said like, no, like, only this one org can right go. Without a whole lot of, like, specific reasoning. But anyway, more recently, just at the end of this last year, kinda right before the winter break, I on a whim, I I was actually trying to prove out a different, like, architecture for a specific application. And I decided like, you know, I well, I actually anytime I'm doing a proof of concept in almost anywhere, I did this at Amazon as well. I just write Go so much easier.
Creed Haymond:It's more I'm more fluent in it than I am even though I write Java every day, the build system is worse. So anyway, I did this proof of concept, rewriting stuff, and and I and used Claude as my bastard hands. And Claude and I, you know, badgered him into getting this proof of concept up. And and it actually formed up so well that I I load tested it and against a similar, like, production load against and and and did a side by side comparison of Java Spring. And it was so good that my manager was like, oh my gosh.
Creed Haymond:Write this up in a proposal because, like, we we could save quite a bit of money and also headaches and all this stuff.
Jonathan Hall:So so when you say it was so good, like, in what by what metrics? It was faster? It was easier to write? It was what?
Creed Haymond:It was yes. All the things. You know, like, obviously okay. Caveat being, like, I'm sure there there's gonna be plenty of, like, language y folks that are like, oh, you well, I'm sure you it's just like an architecture difference. You could squeeze out the same performance in Java if you worked hard enough.
Creed Haymond:But that being said, like, our team was already on on this, like, the cusp of not really wanting to do any more Java Spring. This is just not jiving with them. Also, this whole AI advent of like, hey, look, the language is not it doesn't matter as much. And Go is very explicit, kinda like that article a couple months ago somebody put out there was like, Go is great for anyway. But, yeah, the the benchmarks for even like, I I forced I did my own load testing where I I did one version where I forced a single pod with the same memory and CPU, and I could get, like, 48,000 requests per second.
Creed Haymond:And this isn't just like a hello world. This is like a full fledged, like, the same architecture of this application is doing all the same work. It's mirroring the exact same traffic load as like our production workload. So I could get like 48,000 rps where I could only get like maybe 4,000 out of the spring equivalent with like a quarter of the resources as well. So it was a really fun benchmark, but it honestly was so good that my manager basically was like, hey, let's clean this.
Creed Haymond:Like, knew I I was more just kind of trying to prove like a separate point, but he was like, let's actually write this up and show it to leadership and say like, look, with AI and everything in our
Jonathan Hall:You're trying to prove the architecture, not the language. Right?
Creed Haymond:Yeah. Exactly.
Jonathan Hall:And then he was like, wait, this language is also pretty cool for for this project.
Creed Haymond:Yeah. Worked out great. Speaking of which, the Valky Go client was in this architecture. So actually part of that's part of the reason I'm shout out right there.
Jonathan Hall:Way to go This week you'll be adding GPDF.
Creed Haymond:Exactly. The next one is generating PDFs. What do you know? At a 100 times the speed. But yeah, it was a great experience.
Creed Haymond:And now we're starting to write some of our stuff in Go, starting with just a couple of services that we're already, like, in process of re architecting and going great. Cool. That's a fun story.
Jonathan Hall:So you're you're kind of at the beginning stage, it sounds like, of of, like, making the transition. Like, it's been has it been officially approved that you can start switching to Go now?
Creed Haymond:Stamp of approval.
Jonathan Hall:Yes. And you said that Go has already been used in other teams at Epic. What what what else is it used for other than rendering Fortnite?
Creed Haymond:Yeah. Exactly. The game clients you download are actually Whales apps written in React and Go. Nice. Yeah.
Creed Haymond:The the one team that I'm I'm confident a 100% of their stag is in Go is the EcoSec. So they I believe the ecosystem security team. So they do a lot of security work. I can't even speak to all the things that they're using it for specifically, not on the team. But, yeah, they've been using it for a while.
Creed Haymond:And actually even they were kind of like helped me out in this kinda like pitching go for other things because they were like, we we originally wanted more people to adopt it internally. Not to, like, just take everything over, but in reasonable spots where it made sense. It runs lighter and it runs cheaper and it writes clean. So, yeah, great place. Cool.
Jonathan Hall:As a as a gamer, at what point am I is my gaming experience being affected by Go? Oh. Well,
Creed Haymond:anytime you're trying to match into a session where or even creating a session. Okay. Or when your stats are being saved and and achievements are being earned and leaderboards are being tracked. All of the things that can kind of be done asynchronously outside of the game loop, the hot loop, you know, like, to be honest, this is a don't tell anybody, but I don't actually play very many video games. But I know I know I know.
Creed Haymond:It's kinda crazy. Yet I work here and it is a blast. I absolutely love working here. But but anyway, yeah, there's like the hot game loop where you're trying to keep up FPS, you know, somebody strikes here and you need your, like, game server to actually have that state in the same spot for other people connected to that game. That is not what we're writing.
Creed Haymond:Mhmm. Those servers and sometimes clients like on, you know, people's desktop machines, maybe after a big match, we'll probably batch upload like a number of stats that they earned. And that's where our services are are taking over is like sort of the longer term cross play compatible things that are, you know, saving your achievements here so that they show up on your p s two. I mean, p s four, whatever it's you can know how how up to date I
Jonathan Hall:am. It's like a Playstation. It's just it's just the Playstation. Right? Exactly.
Creed Haymond:Yeah. Playstation, computer, all that stuff.
Jonathan Hall:Yeah. Got it. Cool. Yeah. That that sounds like fun.
Jonathan Hall:So how long have you been using Go?
Creed Haymond:I've been using it since okay. Off and on. Since I was in college, I found it. Let's see. This was back in maybe 2017.
Creed Haymond:I think it was one .5 was the version at the time, one dot five or one dot six. Mhmm. And then I used it at Nozzle where I rubbed shoulders with Derek Laird of the Forge the Go West Conference. Derek Laird and Miriah Peterson. I regularly kind of rub shoulders with them and meet ups here in But, yeah, I've been off and on using it there.
Creed Haymond:I only actually worked full time in it at one job. This was at Nozzle in in Utah, which was great. But I have kept it in my heart and soul. I am a gopher since then. Nice.
Creed Haymond:Cool. And yeah. Been using it for various tools here and there since then. That's awesome.
Jonathan Hall:It's it's fun to get a a peek behind the scenes for a brand that we all are at least familiar with. I mean, I've I've never played Fortnite, but I've tried to play some epic game before. But I certainly do play games occasionally, so it's it's nice to get a sense of, you know, how something like Go is used at a place like that. Now I'm gonna put you on the spot, because I forgot to tell you this ahead of time. Oh, no.
Jonathan Hall:But since since you're now not only a cohost, but an official interviewee, I have to ask you the stumper question.
Creed Haymond:Oh, boy.
Jonathan Hall:And I hope I hope you're you have an answer. Take your time if you don't. The question is, what is your favorite third party Go library?
Creed Haymond:Oh, it's funny because like any other language, and there'd be a thousand of them out there of like Java. It's like Spring is my favorite third party thing because it's not Java. But Go standard library, man. It covers so much that you really gotta stretch for your now, I think I think I wanna say well, you know, the easy answer is saying Valkyko because it's so, you know, recency bias. But outside of that, this is kind of goofy, but tint.
Creed Haymond:Tint is like a log coloring like a log coloring library. And I'm not, like, always a, hey, give me all the flashy rainbow colors of logs normally. To be honest, when we're running in production or whatever, it's always just slog, no colors or anything. It's just regular JSON logging. However, doing stuff locally and running things locally, I might I can't sit there and parse JSON logs.
Creed Haymond:My brain it it explodes. And so I love adding tint for the human readable and, yes, colorized, worn, error, info, debug logs. Just it's it's a great one. Simple.
Jonathan Hall:Answer. I like it. Nice. Yeah. I've used I've used it I don't use it in every project, but I've definitely used it.
Jonathan Hall:That's a good answer. Yeah. Well, Creed, if our listeners are interested in following your epics at epic or reaching out otherwise, can they can they find you on social media, maybe GitHub or something? What's the best place to reach out to you?
Creed Haymond:You can definitely find me on GitHub. That's almost my main form of social media at creedasaurus, t r e e d a s a u r u s. Yeah. Creedasaurus, I'm on LinkedIn. I have an x and maybe a blue sky, I think.
Creed Haymond:But to be honest, I I don't use those very much or the go for slack. I am definitely there.
Jonathan Hall:It's always a good place. Cool. Well, thank you so much, Creed, for stepping in while Shay's gone and talking to us about Go and Epic. It's been a pleasure. Hope to see you again.
Creed Haymond:Appreciate it. Thank you.
Jonathan Hall:Alright. Program exited. Program exited. Goodbye.
Creators and Guests
