Jerod

But as gophers yourselves, I'm curious your thoughts on that sentiment and the landscape of, let's just call them systems-level programming languages, I don't know, general-purpose programming languages in the year of our Lord, 2025. I think I would say that...

But as gophers yourselves, I'm curious your thoughts on that sentiment and the landscape of, let's just call them systems-level programming languages, I don't know, general-purpose programming languages in the year of our Lord, 2025. I think I would say that...

Is the separation garbage collection versus non? Is that the big distinguishing factor?

Is the separation garbage collection versus non? Is that the big distinguishing factor?

Yeah, I think it's tough when simplicity is a core imperative or a principle to compete in a landscape of progress and change and advancement. When you try to keep it simple, and that's hard to do, and also backwards compatible, that's one of those things is like, really strong backwards compat. And eventually that's just like, you, you have no more shiny things to point to over time.

Yeah, I think it's tough when simplicity is a core imperative or a principle to compete in a landscape of progress and change and advancement. When you try to keep it simple, and that's hard to do, and also backwards compatible, that's one of those things is like, really strong backwards compat. And eventually that's just like, you, you have no more shiny things to point to over time.

And people just, they get bored and want to move on. And of course there's good reasons to, to want to move on and then to seek other languages for certain use cases. Or there's, there's also career trajectory to think about. Right. Which honestly drives a lot of our decision-making is like, can I make money doing this and how much? Yeah.

And people just, they get bored and want to move on. And of course there's good reasons to, to want to move on and then to seek other languages for certain use cases. Or there's, there's also career trajectory to think about. Right. Which honestly drives a lot of our decision-making is like, can I make money doing this and how much? Yeah.

That's a lot of what I think developers, the wins we're trying to sniff, even more so than what is purely the best technology for this particular thing I'm trying to do. I don't want to be investing in something that's going to be irrelevant. Or I also would rather make more money than I'm making right now, and all the up-and-coming jobs are TypeScript or Rust or you name it.

That's a lot of what I think developers, the wins we're trying to sniff, even more so than what is purely the best technology for this particular thing I'm trying to do. I don't want to be investing in something that's going to be irrelevant. Or I also would rather make more money than I'm making right now, and all the up-and-coming jobs are TypeScript or Rust or you name it.

But it's just a tough thing. When you're all about simplicity, which is one of Go's main things... When everybody wants to say, what else can you do? It's like, well, I've showed you everything at 25 keywords, you know, you know, I'm already, for instance.

But it's just a tough thing. When you're all about simplicity, which is one of Go's main things... When everybody wants to say, what else can you do? It's like, well, I've showed you everything at 25 keywords, you know, you know, I'm already, for instance.

Let's move up a level, get slightly more hypothetical and imagine a world where the source code that we write today is the bytecode of tomorrow. Chris, I'm sure you're going to be quite skeptical of this future, but there's a lot of money going into making that happen. And potentially it could happen.

Let's move up a level, get slightly more hypothetical and imagine a world where the source code that we write today is the bytecode of tomorrow. Chris, I'm sure you're going to be quite skeptical of this future, but there's a lot of money going into making that happen. And potentially it could happen.

In a world like that, do you think Go thrives when you are outputting Go source code from a maybe more human written instruction set and then you only look at it when you have to kind of a thing?

In a world like that, do you think Go thrives when you are outputting Go source code from a maybe more human written instruction set and then you only look at it when you have to kind of a thing?

Well, you want to go from the non-deterministic step to something deterministic. And so your pros, current state of the art, they're going to produce different output when given repeatedly. And so they're non-deterministic, the output of the machine.

Well, you want to go from the non-deterministic step to something deterministic. And so your pros, current state of the art, they're going to produce different output when given repeatedly. And so they're non-deterministic, the output of the machine.

And so if you can go from there to something that could be deterministic, now I can actually reason about that, which is why I think Go is a decent programming language for something like that. Because now you can look at it and say, okay, here's what I have. based on the prose I wrote, and I've got to flip this bit in order to actually get the outcome, or something like that.

And so if you can go from there to something that could be deterministic, now I can actually reason about that, which is why I think Go is a decent programming language for something like that. Because now you can look at it and say, okay, here's what I have. based on the prose I wrote, and I've got to flip this bit in order to actually get the outcome, or something like that.