Matthew Sanabria

But then when I went there on the other side, I was like, this is actually pretty good. I see why you all are using it. So, if I didn't have that like kind of peer pressure, I probably wouldn't have tried it myself.

But then when I went there on the other side, I was like, this is actually pretty good. I see why you all are using it. So, if I didn't have that like kind of peer pressure, I probably wouldn't have tried it myself.

Yeah, we have a lot of people here like to try bleeding edge tools or at least stay on like the main branch for different tools and build things from source. That's how I found Helix. That's how I found Jujutsu. And, you know, I've kind of started to take this mantra of not just installing my tools using like a package manager, but instead building them from source.

Yeah, we have a lot of people here like to try bleeding edge tools or at least stay on like the main branch for different tools and build things from source. That's how I found Helix. That's how I found Jujutsu. And, you know, I've kind of started to take this mantra of not just installing my tools using like a package manager, but instead building them from source.

And like, it's been really nice. It's kind of like a different paradigm than I'm used to, but it's nice to be able to monitor an issue or something and say, oh, this thing that I was having issues with is fixed. I just build from source. I don't have to wait for them to release anything. This is great. Mm-hmm. So that's kind of the oxide way, so to speak.

And like, it's been really nice. It's kind of like a different paradigm than I'm used to, but it's nice to be able to monitor an issue or something and say, oh, this thing that I was having issues with is fixed. I just build from source. I don't have to wait for them to release anything. This is great. Mm-hmm. So that's kind of the oxide way, so to speak.

And a lot of people, they pull in things that aren't even merged into the default branch, right? Like they'll pull in, they'll go to the main branch and pull in some PRs that are not yet merged and build that. And that's what they daily drive. And I think part of it too is that the commands for building these things now are better than what we used to do in the past, right?

And a lot of people, they pull in things that aren't even merged into the default branch, right? Like they'll pull in, they'll go to the main branch and pull in some PRs that are not yet merged and build that. And that's what they daily drive. And I think part of it too is that the commands for building these things now are better than what we used to do in the past, right?

Like you can just, like Ghosty is just one zig build away from using it and having a nice binary. And same thing with like Helix. You just cargo build it, right? And you install it and it's done. You don't have to really worry about, you know, autoconf, configure, make and all that stuff. You just use the tooling for the language and you have everything you need, which is much nicer. Yeah.

Like you can just, like Ghosty is just one zig build away from using it and having a nice binary. And same thing with like Helix. You just cargo build it, right? And you install it and it's done. You don't have to really worry about, you know, autoconf, configure, make and all that stuff. You just use the tooling for the language and you have everything you need, which is much nicer. Yeah.

Do you agree, Matthew? Yeah, I agree overall. I think part of the negative attention Go is getting right now I think has to do with the cloud repatriation effort that's going on, where people are just kind of fed up with the cloud in general.

Do you agree, Matthew? Yeah, I agree overall. I think part of the negative attention Go is getting right now I think has to do with the cloud repatriation effort that's going on, where people are just kind of fed up with the cloud in general.

And since Go is more of that cloud-focused language, people by definition are fed up with the tools around the cloud too, and Go just kind of gets caught up in the middle. And Go is a simple language, right? There's something to be said about the average developer being able to read a piece of Go code and understand it because it's a simple language.

And since Go is more of that cloud-focused language, people by definition are fed up with the tools around the cloud too, and Go just kind of gets caught up in the middle. And Go is a simple language, right? There's something to be said about the average developer being able to read a piece of Go code and understand it because it's a simple language.

But also, I know that it doesn't have all the bells and whistles like other languages that it's competing with does, right? Like, you don't have reduce and fold or whatever. You don't have, you know, true iterators like that or true generics. They all feel like bolt-ons to the language. And, like, I'm at Oxide, right? And we build a cloud computer.

But also, I know that it doesn't have all the bells and whistles like other languages that it's competing with does, right? Like, you don't have reduce and fold or whatever. You don't have, you know, true iterators like that or true generics. They all feel like bolt-ons to the language. And, like, I'm at Oxide, right? And we build a cloud computer.

And you would think that cloud and Go go hand in hand. And that's very true. But most of Oxide is written in Rust. But we do have a lot of Go in the places where we have to integrate. So think like Kubernetes integrations, Terraform integrations, Packer integrations, all of that stuff is still Go. So I'm responsible for all that at HashiCorp, or sorry, HashiCorp at Oxide.

And you would think that cloud and Go go hand in hand. And that's very true. But most of Oxide is written in Rust. But we do have a lot of Go in the places where we have to integrate. So think like Kubernetes integrations, Terraform integrations, Packer integrations, all of that stuff is still Go. So I'm responsible for all that at HashiCorp, or sorry, HashiCorp at Oxide.

And it's like, that's all going to be Go stuff, right? You don't write that stuff in Rust because all of the integration points are Go and have Go libraries for that. So I don't know. I think the kind of negative attention Go is getting is somewhat warranted because it is a language that hasn't really evolved so, so much in comparison to its competitors.

And it's like, that's all going to be Go stuff, right? You don't write that stuff in Rust because all of the integration points are Go and have Go libraries for that. So I don't know. I think the kind of negative attention Go is getting is somewhat warranted because it is a language that hasn't really evolved so, so much in comparison to its competitors.