ʕ◔ϖ◔ʔ -> 🦀 Rust GOes Async, Survey says LLMs aren't all over, & new questions

Episode Transcript
Available transcripts are automatically generated. Complete accuracy is not guaranteed.
Shay Nehmad (00:00):
This show is supported by you. Stick around
till the ad break to hear moreabout that. This is Keppa Go for
January 3rd 2025. Fixing the2024 that's written in our notes

(00:21):
right now. And everybody wholistens and has a website or a
company, go change the footer aswell.
Keep up to date with theimportant happenings in the Go
community in about 15 minutesper week. I'm Shayne Ahmad.

Jonathan Hall (00:33):
And I'm Jonathan Hall.

Happy New Year.

Hey. Happy New Year.

Empty notebook. 365 pages in it. What are you gonna
write? I heard this promotion onthe radio. I think it was New
York Times or The Daily orsomething.

Uh-huh.

An ad. I really liked it. It's a cool ad. So we
have a huge ass backlog ofthings to talk about from the
holiday season. We took a break.
We tried to pick the top thingsthat we thought would be
interesting for this week. We'regonna talk about a meetup. We're
gonna talk about some lectures.We're gonna talk about some blog
posts, and we're gonna go intothe dev survey results. I'm sure

(01:12):
all of you voted and now you cansee, if you voted correctly and
if you have your finger on thezeitgeist.
And since this is a new year,we're gonna have to come up with
a new stumper question for ourinterviewees. So we legitimately
don't know what it's gonna beyet, and you're gonna discover
that it alongside us. That wasclunky. Let's go to news because

(01:36):
we know how to do that.

So, first up, as you mentioned, there's a meetup.
I wanna talk about, the Irish GoFirst are getting together
again. This is the relaunch ofGo Ireland, in, in Dublin,
February 6th. So you have timeif you're in the area. We're
talking about benchmarking Go atthis one.

(01:59):
This year, relaunch, I don'tknow how long it's been since
the last one. I don't know ifit's been since pre COVID. It
was been that long or not, butif you're an Irish gopher and I
know several. I used to workwith a bunch of Irish gophers
because I I worked for an Irishcompany. So maybe some of my
buddies will be there.

Alright. I love Dublin. I'd go Nice city. Back.
Yeah.
Yeah. And, of course, you couldyou should check it's a new
year, whatever, coming back fromholidays, wherever you are,
like, in whatever city you areor country you are, look for
your Go community and go to ameetup. It's gonna be cool. It's
almost always worth it,especially since the food is

(02:37):
free. So, like, what can youlose?
Worst case you're eating someshitty pizza. But, yeah, it's
good stuff. I wanna talk about ablog post I found.

Let's do it.

That I found really interesting because this year,
it's not a New Year'sresolution. I don't really
believe in those, but do youknow, I'm blanking. That guy on
YouTube does explainer videosstick figure. Super popular. CGP
Grey.

Okay.

That guy. He has a podcast, that I really like
called, Hello Internet orsomething like that where he
talks about not doing a yearlyresolutions, doing themes. What
the theme of the year. My themeof the year is being less
dogmatic about languages. Thisblog post just is all about that
because I'm not gonna beprogramming in Go a lot this

(03:24):
year even though I really likeit, and I think this is fine.
Right? I wanna be at peace withthat. And this blog post from
Alexander Fadayev, I found itreally towards that sentiment of
let's take good things fromlanguages and try to make them
work together instead of being,like, very tribal about this is
the best language and I'm gonnadie on this hill, whatever. It's

(03:44):
Rust goes async. Usually, when Itry to get back into Rust, like,
once a year when I'm trying tofeel smart, I start doing it and
then I stop.
And I stop at Async because it'svery difficult and I know, and
I'm, like, doing air quoteshere, that Async Rust is
notoriously difficult and looksreally ugly. I don't know how

(04:05):
much experience you've hadtrying to write Rust at all or,
like, async Rust.

I've never done Rust, but I did some async in
other languages that wasdefinitely a pain in the butt.

Versus go where right? That's the whole that's
the whole point. You wanna starta, you know, you're not spawn
spawn a task, literally writethe word go. You wanna do some
communication, open a channeland literally put the arrow sign
on it. I don't know if you havea glyphs in your, like, terminal
or editor that make the arrowlook nice, or are you using,

(04:34):
like,

a normal one? I've definitely seen that. I
don't think I have that maple,in my current configuration.

I've just set up a ghosty, that new editor, that
new terminal emulatoreverybody's raving about and it
has that built in. I really likethat. Anyway, so, you know, the
whole concurrency thing looksreally good in Go. This blog
post just suggests a mind mapthat shows if you know how to do
a thing in Go, for example,setting up a channel, here's how
you did that in Rust, just theequivalent syntax, which I found

(05:02):
super super useful and it reallymakes reading Async Rust a lot
easier for me. Just shows anexample from the Go
documentation and then the Rustequivalent and it literally
physically drawing arrows fromthe Go code to the Rust code to
sort of help you do that mentalmapping which I really really
liked.
For example, in go, you wouldsay go and then call a function

(05:25):
say and pass the parameterworld. In Rust, you would spot
like, do Tokyo, colon colonspawn, then pass in a function
call, like, say, hello world.With Tokyo and with the async
std, what are the cargo thingscalled? I think packages.
Crates, sorry, crates.

Yes.

And the the mapping between select in Go and Tokyo
select in Rust, even with atiny, you know, gopher in ASCII,
the thing that we talked aboutin the past is a potential file
extension

Yes.

Versus Rust, which gets a, like, a top level emoji
with a crab. You know what Imean? Because it's a crustacean.
So just equivalents, reallyreally simple short blog post.
If you're doing, Rust and you'rehaving trouble with async and
you know go pretty well, this isjust gonna be the, like, missing
link part of the puzzle for you.
And as always, whenever there'sa really good blog post, I sort

(06:21):
of went and dug throughAlexander's blog, and it's
pretty good, like, aboutdevelopment and cybersecurity.
Go read more of his, blog post.And, Alexander, if you're
hearing this, make more of them,please.

Yeah. That's pretty cool. I like that post.
Yeah. I haven't I haven't donerest yet, but

Maybe in 2025. Who knows?

May maybe it could happen.

Talking about things that will happen in 2025,
I have good money that we'regonna have 2 surveys about 2025.

That seems like a good guess. Probably 2 go
releases as well. 2 major ones.

Yeah. And one huge cyber security bug that's gonna
cause blue screens all over theworld for me. That was crazy.
That was 2024. Feels like agesago, that that CrowdStrike
thing.
Well, if only they've written ina better language. Speaking of
better languages, talk about theGoDev survey. We actually had

(07:15):
the the author of the survey orthe people behind the survey on
the show.

Yeah. We had Alice Merrick on, several months
ago. So I'll put a link to theshow notes in this we'll put a
link in the show notes to thatinterview if you wanna, refresh
your memory or if you missedthat one talking about what goes
into the survey and what they'retrying to learn and how they do
that and and other good things.

Yeah. That was that was a really good talk.

I'm interested in the experience of using tools,
you know, for humans and, otherkinds of technologies. Sure.
Wonderful. I think this is mylast question before we talk
about the survey.

So some of the things are to be expected.
Right? People who answered thesurvey like Go.

Yeah. Yeah. That's not a surprise. 90 some
odd percent, are satisfied withGo. 4% are dissatisfied.

I would love to meet these people.

Yeah. Who's who was so dissatisfied that they're
answering the survey in thefirst place? Of course,
everybody uses Linux, 61%. 59%use macOS. You might notice that
as it's more than a 100 already.
I guess people like to use more

than 1 operating system. And the 24% on Windows,
that's more than I would haveexpected. Yeah.

And then and then WSL is its own category. That's
15%. So that's interesting.Yeah.

Because it's not really Linux. I think people who
do WSL might answer Windows byaccident, but they actually
like, the whole toolchain is isLinux ish.

Mhmm. Mhmm.

But the deployment environment has been and stayed
Linux. People deploy Go usuallyto the cloud and containerized
workloads, so it's all runningon on Linux. And I assume even
people who said Windows and MacOS might be mistaken. Like, I
assume there's some error ratehere with more of the beginners
thinking they're deploying toWindows, because I don't know,

(09:05):
they're deploying to Azure Cloudin their company or or whatever.

Right. Right. Right.

Yeah. Interesting. And, architectures was a
question for for, like,different deployment categories,
which I found surprising. Like,who but but I guess it's
important. Right?
You need to know whicharchitectures to optimize for or
whatever. But I think this is asas a survey question, it's
pretty funny because you shouldhave telemetry at this point

(09:31):
giving you real answers. True.Maybe comparing the reported
data to the actual data can tellyou who's not answering the
survey. Right?
Just people who are compilingfor, I, 386 architectures, they
they hate answering surveys. Sowhat have you found which was
sort of new?

So what I think is interesting though is that
they follow this up with anotherquestion. This one I believe has
been asked, over the previousyears, which is what is your
preferred editor for Go? And I'mI'm not really sure what to make
of the difference here. So theydo mean, as you suggested, Shai,
that that they, there is apotential bias. Yeah.
Right. Almost certainly a biasbecause, they ask people who use

(10:12):
Versus Code or Golang. They'rethey're, like, prompted to fill
out the survey. So I don't thinkthey did it with, Emacs and and
Vim. But the second question is,what is your preferred editor?
Versus Code ranks the highest,38%, DOLAN second, 35, and VIM
third at 17%. So the ranking isthe same as those who use it

(10:34):
regularly, but it looks asthough 66% of people use Versus
Code regularly, but only 38%prefer to use Versus Code. So
I'm sure that this selectionbias is playing in here somehow.
I'm not quite sure what thatmeans, though. It's it's an
interesting disparity.

I think, like, preferred is is such a, is such
a loaded term because I think mypreferred editor is, like, a
fully decked out Vim with, GoPLSand the tags and everything
working and all the shortcutsjust because it works really
fast and it looks really goodand whatever. But I experienced

(11:16):
some sort of moving betweenmachines a lot and companies a
lot and whatever and Versus codewith Vim bindings just works.
And it works, you know, in theweb editor if you're suddenly
need to work on someone else'smachine, you just go into GitHub
and you, like, press dot andopens the web editor with your
extensions and everything youlike. So I've definitely used

(11:36):
Versus Code for Go development aton. The killer feature for me,
at least this year, was AIcompletion.
Right? Copilot, which Vimdoesn't have. So I've basically
relegated Vim just for, like,quick file editing or editing
where I don't need to do where Ineed to do a lot of searching,
search and replacing, macros,things like that, or git commits

(11:58):
and and, like, that's it. I Idon't use it for anything else,
both for Go and Python, by theway, which were my main
languages, like, this year. Butif if you I I think I enjoy,
like, working in Vim more.
It feels more crafty than VersusCode. But as a daily driver,
Versus Code, no problem. Onething is I don't get is why
people like Golang. I just hatethese intelligent editors.

(12:21):
What's your preferred, editorfor this?

Versus Code is the one I use the most or
something that I don't likeabout it. I was a big Atom fan
before it was abandoned. So I'venever heard of it. Helix.

I never even heard of it. I'm gonna I'm gonna give
it a try right now. I triedGhosty, the new editor, and I
was pretty pleased with it.Postmodern text editor. That's a
bit pretentious.

The first the first FAQ. Postmodern? It's a
joke. If Neovim is the modernVim, then Helix is the
postmodern.

Good. Good. Good stuff. Built in Rust for the
terminal. No Electron.
I like how the fact that we'renot bringing Chromium alongside
with your app is now a featurefor for software. I mean, it is
true. But yeah. I think the themain thing is to not be tribal
about this stuff and be excitedabout trying new, editors and

(13:15):
picking out features. I've,like, tried Emacs for a while
when I tried to learn Closure.
Dude, that was really cool.Like, I wasn't productive in it,
and I I had a really hard time,but seeing people, like, being
obsessive about theirconfigurations for years years
and getting really productive ina specific editor was really
cool. I don't like it. I stilldon't like IntelliJ, though.

(13:37):
Unless they wanna sponsor this,show.
In which case, I'm gonna be thebiggest chill on the planet for,
a slow editor that spends a halfof the time doing, like, the
index indexing thing and messesup Go Go modules all the time.

Yeah. Let's talk about one other aspect of this,
survey before I move on to othertopics. One of the new questions
was about, Go for Teams. And,the question that I I wanna call
out here is, at work, to whatextent do the following
challenges impact your currentteams' experiences in Go? And
the highest ranked one wasmaintaining consistent coding

(14:13):
standards across our Go codebase with 23% saying it was
significant challenge for theirteam and an additional 35 saying
it was a minor challenge.
That's more than half thoughtthat was a challenge. I find
that surprising because Go codestandards, I don't I mean, like,
GoFund and and even just thesort of opinionated nature of of
the Go ecosystem seems likethere should be a much smaller

(14:34):
problem for Go than many otherlanguages. But it still seems to
be a struggle for well overhalf.

I think the the code standards is not about the
the formatting. Right? Peopledon't care about the white
space, and I think it's moreabout people who come into Go
from other languages. I've seenthat a lot at work where I've
successfully converted quite alot of Python engineers into Go,

(15:01):
developers, Go engineers. Youknow, you bring your sort of a
sort of conceptions about how agood code looks.
Right? Like, clean code and howcode should be arranged and what
abstractions you should thinkabout. And you, like, would
start with planning out how theobjects and classes would look
like first, which is not very Goish. Anybody who's coming from a

(15:24):
dynamically typed languages, forexample, takes a while to, like,
figure out exactly when to use atype alias. And, you know, just
this week, I had to, talk tosomeone about yeah.
Goat doesn't really have enumsand it sucks. And you need to
think about cogeneration if youreally wanna make it work.
People come from Java or Ruby orPython are gonna have a a

(15:45):
difficult time, like, writing goish go. I hate the word, like,
idiomatic, but if you have onego ish gopher in your team and 1
Python ish gopher in your team,it's gonna be, like, difficult
to maintain a code base and sortof justify the the Go state of

(16:05):
state of mind because it ittakes a while to get used to it.
Know what I mean?
The the fact that the forexample, inheritance is not such
a big thing. You know, peoplelearned in university
inheritance and then worked inJava for 4 years. There they
have the the object orientedbrain rot. It's hard to get over
it. No shade if you're writingin Java right now, of course.

(16:26):
One question I foundinteresting, even though it was
super obvious that it's going tobe asked this year, is about AI.
What do you do with AI and go?Of course, AI, AI, AI. Everybody
needs to justify theirvaluations and their GPUs that
they bought this year, but Ilike the way they approached it,
like, what AI, usages peoplehave done. First of all, the the

(16:50):
thing that is blowing my mindthat people are not using LLM
assistance for writing Go in thelast month is 30% of the people
who answer.
Are you in that cohort of, like,not using Copilot?

Yeah. Quite heavily.

So I'm I'm I I really am struggling to
understand people who have notused an LLM for writing Go for a
month if they codeprofessionally or even for like,
only if you're a student and youjust wanna sort of grind through
the syntax to really learn it atthis specific month. That

(17:25):
shouldn't be 30% of the peopleanswering this survey. Right? So
I I

I would love to see, like, the the experience
like, like, the the the crosssection. What's their experience
level and and their age comparedto this question? Are these the
really experienced engineers whoare like, I don't need LLMs. I
already know what I'm doing. Oris it the the people who haven't
just learned it yet?
I'm really curious.

So the actually, people who don't use an LLM are
the more experienced accordingto the survey. Like, people who
are less experienced tend to notanswer this. 25% of people who
are up to 2 years of experiencedon't use an LLM. 33% of people
who are 5 years 5 plus years ofexperience don't use an LLM. It

(18:11):
also the breakdown of where theywork is interesting.
Solo developers and largeorganizations. If you're in a
medium or small organization,you, don't answer that. Again,
relatively. And I was just supersurprised because I've been
using it for the rest of theexamples here, like, the top one
is code completion, writingtests, which I don't do that

(18:34):
much with AI to be honestbecause I like writing my test
TDD and, like, thinking aboutthem. But definitely the boiler
plate and, like, coming up withmore cases for sure.
Generating go from, naturallanguage description, I've
definitely given, like, Claude abroad, hey, start writing this
script for me. It goes tobackstage API and GitHub API

(18:55):
blah blah blah. It just roughsout, you know, fine I don't
know, like, please put thereferences in the in the
comments above each API call soI can actually fix your mistakes
for you just to rough out thethe start. And as you go down
the list, it it's more esotericcases like resolving compiler
errors or debugging failures orsuggesting libraries or

(19:16):
converting code from anotherprogramming languages. I found
this interesting.
I assume the numbers are arereally gonna change pretty fast.
Like, people who don't use LLMsat all are gonna become sort of
fringe just because as themodels become better and it
people become better at usingit, I just I can't see it going
any other way. Although, I mightbe wrong.

Oh, I I think pretty soon the people who
answer no will be will be thepeople who don't realize they're
using it even though they are.

What do you mean? Like, how could you I

I I think l LLMs are gonna be built into so many
things. Like, if you're usingVersus code, you'll probably be
using or or or go land, oreventually, you'll be using LLMs
without even realizing it. It'sautocomplete and just a lot of
the built in features

Code review and whatever.

Yeah. I think I think we won't realize we're
using LLMs.

That might be the case, or your boss might be
replaced with a LOM thatgenerates the Jira tickets for
you. And I don't wanna be, youknow, like scary old AI. I think
it's called AI doomers at thispoint, but I've seen, have you
had a chance to play aroundwith, Devon? Hashtag not

(20:22):
sponsored. It's sort of like,you don't you give it the test
cases and the setup and you andyou make sure it it has a dev
container it can run on and thenit does the tasks for you.
Takes, like, 2 hours and it, inmy experience, about 20% of the
time can finish a a junior onestory point task in about a day.

(20:45):
Like, I'm not this is a this isa huge advancement. Right? I'm
not knocking it's not good. It'snot good.
But it might be better than thedeveloper who says I have 0
years of experience, and I don'tuse NLMs, at least at this point
in time. Yeah. If you work hardand, I don't know, you do
boot.dev and you and you grindout Lee Code and you read books

(21:05):
and you get better and youlisten to the podcast blah blah
blah. Like, you will be betterpretty quickly than the AI
tooling is. But not knowing howto use it, I I just don't get
it.
Especially, since really strongdevelopers are using it as well.
It it doesn't necessarily meanyou'll be a weak developer,
whatever that means. Anyway, thesurvey is out. These are
obviously just our opinions anddeveloper sentiment towards Go

(21:29):
is very positive still, which isnot surprising at all. Alright.
We have a huge backlog still,but this, is a short show, and
we have to cut things somewhere.Let's move to the lightning
round. Lightning round.

You go first. Do you have a video you wanna talk
about?

I have 2 actually. So my first, item for lightning
round is, best practices ofusing Go and Prometheus in
Kubernetes. Unfortunately, it'sa Hebrew lecture so only if you
speak Hebrew you can, watch itand I don't think it even has,
like, closed captions. But it'sa really good talk, in the Go
Israel meetup and I just wantedto shout it out from Aviv

(22:11):
Littmann. It was, this month atthe Dell.
Just go powered Prometheusmonitoring, best practices for
Kubernetes operators. Supersuper useful, and a pretty good
talk. Way to go, Aviv. Go watchit. Next up we have 2 items to
sort of talk about the samething.
Right? So I found this, video,create a Golang desktop

(22:33):
application with whales andreact. And you wanted to mention
a new tool called gRPCmd GUI.

Right? Yes. Yeah. I I found this tool just
recently. It's a, modern crossplatform desktop app for gRPC
API development and testing.
I haven't played with it yet, soit may be crap, but it looks
cool. And it's built usingWANES. So

What is WANES?

What is WANES?

Is it like FINE? Is it like a It's it's

kind of like FINE. I I would say it's more
like Electron. So it certainly,there's an overlap with fine and
that it's about building desktopapplications in Go, but it uses,

what It uses Chrome. It uses Chrome.

Yeah. I think it uses Chrome under the hood and
it uses web technologies. Soyou'll be writing CSS and HTML
and stuff like that. But insteadof writing in JavaScript and
Node JS as you would forElectron, you can write all your
code and go.

Well, the definitely, the site for, gRPCmd
looks really fancy schmancy. Andthe video is pretty cool as
well. There's a link in the inthe show notes is from, Bayram.
I just found it interesting.There's a gitabrepo super
technical video, 30 minutes,just mostly you're looking at
Versus Code.

(23:50):
I like these sort of, videoswhere someone just sort of
shares a screen, you know,screen sharing of their laptop
just working on a thing. I don'tknow if I'll use it, but it
definitely seems interesting,especially if you're doing,
like, web slash app application,like desktop application, GUI
application, you shoulddefinitely at least check this
out. Cool. So a couple ofdesktop stuff, not not our

(24:14):
usual, thing, with Go, but, veryinteresting if you're into, app
development. Alright.
Let's jump to a quick ad break.

Alright. Thanks for listening to Cup of Go. You
can always reach us on the webat cup of go dot dev. You can
find us on Slack, the go forSlack at the cup o go kebab
case, channel. You can email usat news at cup of go dot dev.
You can buy swag at cup of godot dev.

And I wanna give a note about the swag. It is now
following the general productsafety regulations, requested by
the European Union. So you canget your mug with the required
safety regulations. Stay safeout there, everybody in the EU.

(25:09):
Meanwhile, cuts to US.
Literally, the president isgetting shot, cars exploding, no
holds, no bars, no laws, UFCfights.

That's right.

Dana White and Joe Rogan screaming at the top of
their voice. Cut to the EUcouncil. We really think
Jonathan and Shai should putmore safety labels on their mug.
People could get hurt. Anyway,so we did the thing.
I said I'll do, like, 2 monthsago, and now you can buy our
swag in the EU again. So buy ourswag in the EU again. We have
cups. We have a t shirt. We havea hoodie, which is my number one

(25:44):
worn item for 2024 just becauseI had one at the office at every
given day, and the the whiteversion, which I really like.
We have some stickers. Shout outto Ariel Kurtz, who just got, 2
stickers for free. Has beenlistening to the show recently.
If you schmooze me enough, oryour wife works at my team at
work, you might get some freestickers as well. But there

(26:07):
there are less roundabout waysto get them.
Just go to the swag store andget some. And what else? Oh, we
have a wireless charger. I'm notsaying wireless chargers because
we literally sold 1.

Sold 1. Yes. Yes.

And I like at home, I have just the Amazon Basics
ones. So I won't I won't getone. Yeah. So you can get some
swag. We thought about doingsome promotions or whatever, but
we couldn't find any good theme.
So if you have any idea for apromotion, let us know. We'll
we'll might do one. Because wemissed the birthday.

You did. Yeah.

Alright. So that's about the swag. What else?

Yeah. Leave a review on Spotify, Apple
Podcasts, or wherever you listento your podcasts.

For sure. For sure. That helps us, climb the ranks.

If you'd like to support us more directly, this
is a kind of expensive hobby forus. Can also become a Patreon.
Don't we have a new one, Shay?

Yes. We do have a new Patreon member, jose_d_s.
Thanks for joining our our,beautiful Patreon. Thank you for
your patronage.

Yeah.

I guess that's a good way to say it. Yeah. It's
$8 a month. Helps cover editingfees, hosting fees, and just
sorta our time that goes intothe show. And finally, you can
also share the show with, like,a friend or a colleague or a co
student or whatever, just to getit spread the word around.
We're nearing up, 20 25 is gonnabe our 3rd year of doing this

(27:30):
show, which is pretty insane.

It is pretty insane.

And we're also nearing up on the 100th episode.
And your support has been,definitely instrumental in
keeping this going andincreasing its quality by, like,
hiring an editor and and doingall this cool stuff. So thanks a
lot for that.

And I think we'll we'll be talking about, sort of
brainstorming, our our next yearand the next segment. So if you
wanna stick around just withthat, don't worry.

A bit of a meta conversation, if you will.
Alright? Alright. We have thisnew year coming up. It will
include episodes.
It will definitely include news,and it will include interviews.
Our 1st year of doing this show,we had a stumper question.

Your answers to our standard questions that we
ask all of our guests on thisshow. If somebody held a gun to
your head that, Adelina, youmust remove some feature from
Go, what would you take out?

And from the other side, this is what you would
remove, but what feature ismissing? What feature would you
take from other programminglanguages or libraries then put
into Go? And back then, it wasabout features. Right? And we
ended up just asking enoughpeople all of the features on
both of the lists.
Yes. Then 2024, we changed it upinto actually, you came up with

(28:55):
this one, which I really like,about sort of how they started.

Yeah. What was the your biggest surprise or or
challenge when learning Go?

And we need to come up with a new one for 2025.
That's the stumper question.

What's the stumper question? What should we
ask you to stump you?

I'm I'm wondering. I think maybe we can take it
like, the first two questionshave been about what do you
think, about Go. Right? Like,how did Go affect you? Maybe we
can do it the other way around.
Maybe you could be like, what isyour work or your contribution
or whatever is doing for Go?Like, how what effects would you

(29:38):
like to see on the Go communityor the Go language that relate
to you? Like, if we interviewsomeone, does meetups or or a
open source package. But maybesome people just program and
they don't really wanna affectthe Go language.

Maybe it would a a a separate question. This
might be too selective.

Why do you also hate, JetBrains?

How will you most be remembered by the Go
community? Something along

those lines.

I'm so excited. Yeah. It's not quite quite what
I'm going for, but what what'swhat's the contribution what's
the greatest contribution you'vemade to the Go community? The
problem is it's kind of aleading question and, like, some
people aren't gonna becomfortable answering that even
if they have made a bigcontribution.

I think that the Go community thing really
suggested, like, open source andtalks and things like that. But
a lot of the contribution couldbe I've mentored someone at work
or I've hired someone. So that'sa good option. You know what? We
did at the survey, we did, whatdo you use AI assistance for?
Right? Let me do that. Put on,like, elevator music while I'm

(30:42):
typing. What is a good generalinterview question about a
programming language? In thiscase, go The previous 2 for
interviewing someone, interviewfor a podcast.

(31:05):
The previous two questions were,one, if you were to remove a
feature and add a feature to Go,what would they be? The fact
that it was a 2 parter waspretty difficult. I like to keep
it like the 2nd year what we hadjust what was challenging was

(31:27):
better. What was challengingwhen you started.

If we'd been smarter, we would have done what
would you add for 1 year andwhat would you remove for
another year?

Yeah. 1 year of positive stuff and 1 year of
shitting on the language.Alright. The AI is syncing.
Well, it is syncing.
I I just figured out We could doit the other way around, and we
could be, like, who was theperson who influenced like,
influenced you the most, like,regarding Go?

Yeah. I like that one.

The thing about, like, favorite questions, like,
who's your favorite whatever,they're not they're not great
as, like, conversation starters,but they're great as as
conversation enders. Who do youwanna shout out? Who do you
wanna

Who's your favorite Go podcast host?

I think that's gonna

That would definitely end a lot of
conversations and maybe somerelationships.

A house divided. A podcast divided surely cannot
stand.

So I had an I had an idea for a silly question. I
don't know. I don't think thisis good enough for a year, but
we could do it once twice. Andthat would be, what do you think
of the gopher?

What do you mean? The the Just a mascot?

What yeah. What's your opinion on the on the on
the mascot? That'd be a funquestion. I don't think it's one
we should do every time. I thinkwe're gonna get 2 or 3

I don't have any opinions about the mascot. It's
just

just I've

looked at it for 10 years at this point. It's just
Yeah. Is the the mascot. Right?I think I think what influenced
you the most or or who, like,who do you wanna shout out in
the Go community or at work orwhatever?

Yeah. I like the I like that one. I like maybe
who has influenced you the mostin your Go journey or something
along those lines.

Let's let's try to refine that. So, like, who
influenced you the most? Thatcould be interesting because it
could be an influencer, like,literally that guy on YouTube
who does what's his name?Primogenogen, whatever.

Yeah. Yeah.

Just people, like, who actually or us. Right?
People who do content. Mhmm.Although we just tell news.
So I I I'd be surprised to hearif we actually influence
someone. Because we're trying tobe unbiased, unless we're
talking about JetBrains, ofcourse. Right. Me just tanking
the possibility of them ever,like

Oh, that shit is sales. Sponsored in the show.
They're never gonna sponsor us.

And it could be, like, oh, my previous boss at
work who introduced me to Go andcould be, oh, I had a conference
talk this year which reallyinspired me. And it could even
be, like, oh, the series of blogposts or I just saw this person
maintaining this library and Iwas so I'm I'm interested. I
people I wonder if most peoplehave that. Let let me stump you.

(34:08):
Who's the person who influencedyour Go journey the most?

If I had to point to a single person, it would
probably be Dave Cheney.

Dave Cheney.

Yeah. So you can plug those. Some of his blog
posts were really instrumentalwhen I was starting with Go and
it wouldn't, influence the way Ithink about Go. Error handling,
I remember, is one of his blogposts, blogging, some of that
stuff.

That's good. That's good. That's a good, like,
stumper conversation editorbecause it it it it puts a nice
ribbon over all the

So how about you? How would you answer the
question? Who has been thebiggest influence on you with
regard to Go?

Well, it's a bit cheesy because you're asking,
but I guess it's you. Because II've like, I've written Go
because of people in the army,and I've chosen it for my
previous startup, which was abig influence. But I looked at
it just as another programminglanguage and not as a community
and, an endeavor and a thing toactually learn and take part of.

(35:09):
Like, I thought about Go in thesame way I think about, like,
terminals today. Just a thing Iuse.
Right?

Right. Right.

And I have my favorite, and I know which ones
are slow and which ones are fastand the and, like, whatever. But
it it was just a a tool for me.And just working with you on the
podcast and meeting all thesepeople and then flying out to,
like, Amsterdam and actuallymeeting you in person, these are
things that have completelychanged my, Go journey from just

(35:36):
being an okay ish Go developerto being, like, a person in the
Go community and taking part inthe meetups and whatever.

That reminds me I wanted

to start that.

That reminds me of I'm wanting to start a
podcast about terminal news. Doyou wanna help me with that?

Like JFK, LaGuardia. This week, Tom Hanks'
character is still stuckcollecting quarters. Alright. I
think we have it.

I think we've had a good question. Yeah. Let's see
how the community reacts. Theyhave a chance to to tell us it's
a it's a terrible idea beforeour first interview, but I I
think I like it.

For sure. Who is the person who's been the
biggest influence in your, Gojourney? I'll try to refine it a
bit more for for our firstinterview in 2025. And yeah.
Happy New Year.
Thanks for listening, everybody.We're back on track. We should
be back to regularly scheduledprogramming until our 100th

(36:32):
episode, which should be, like,a month

Yeah. From now,

something like that, a month and a half, where
we plan to do a huge liveBonanza episode. Make sure to
not miss that. When once we havea date, we'll put it on the
calendar. And I think that's itfor us.

Alright. Good to see you again, Chime.

Good to listen to you 2. This is they don't see
the audio of the rest of thepeople. You know what I mean?

Yeah. True.

Program exited. Goodbye.

All Episodes

Episode Transcript

Popular Podcasts

On Purpose with Jay Shetty

Stuff You Should Know

Dateline NBC

.css-15opob5{left:0;position:absolute;top:0.8rem;} All Episodes

.css-14f5ked{margin:0;word-break:break-word;display:-webkit-box;-webkit-box-orient:vertical;box-orient:vertical;-webkit-line-clamp:2;overflow:hidden;}ʕ◔ϖ◔ʔ -> 🦀 Rust GOes Async, Survey says LLMs aren't all over, & new questions

Episode Transcript

Popular Podcasts

.css-r6mb8g{margin:0;word-break:break-word;display:-webkit-box;-webkit-box-orient:vertical;box-orient:vertical;-webkit-line-clamp:1;overflow:hidden;}On Purpose with Jay Shetty

Stuff You Should Know

Dateline NBC

All Episodes

ʕ◔ϖ◔ʔ -> 🦀 Rust GOes Async, Survey says LLMs aren't all over, & new questions

On Purpose with Jay Shetty