Kris Brandow

Um, and so I was just like, you know what, I'm just, I'm just going to use audition and I'll just deal with this weird flipping between final cut and audition. I think I've gotten it down after editing a few episodes. Now it was kind of a mass jumping back and forth between the two. Um, But I think I figured it out now, gotten it down.

Um, and so I was just like, you know what, I'm just, I'm just going to use audition and I'll just deal with this weird flipping between final cut and audition. I think I've gotten it down after editing a few episodes. Now it was kind of a mass jumping back and forth between the two. Um, But I think I figured it out now, gotten it down.

I have not. I'm kind of, you know, I sat down, I learned Git very deeply. So I mean, I personally don't find much problem with the Git CLI and how everything works. You can see why it's difficult for new people to kind of get in and figure it out. But for me, I'm just like, Git works well enough for this class of version control system.

I have not. I'm kind of, you know, I sat down, I learned Git very deeply. So I mean, I personally don't find much problem with the Git CLI and how everything works. You can see why it's difficult for new people to kind of get in and figure it out. But for me, I'm just like, Git works well enough for this class of version control system.

I do think that some of the work that is being done by places like Ink and Switch to try and find a more like I guess less a source code and more of a prose style of version control.

I do think that some of the work that is being done by places like Ink and Switch to try and find a more like I guess less a source code and more of a prose style of version control.

I'm super interested in that the kind of continual we're always kind of keeping track of what you're doing and then you kind of snapshot it and you can upload those snapshots like I like that kind of seamless workflow. But as far as how we kind of move

I'm super interested in that the kind of continual we're always kind of keeping track of what you're doing and then you kind of snapshot it and you can upload those snapshots like I like that kind of seamless workflow. But as far as how we kind of move

source code around at the moment how we do source code version control i think that git is pretty much like the the best underlying platform and since i'm already so familiar with the tooling i just i don't really look for something new if you know my workflow isn't broken if i'm not it's not painful at the moment which for me it's not

source code around at the moment how we do source code version control i think that git is pretty much like the the best underlying platform and since i'm already so familiar with the tooling i just i don't really look for something new if you know my workflow isn't broken if i'm not it's not painful at the moment which for me it's not

I would say Go is a systems language, but it is more of a cloud systems language than a low-level systems language. I think that's where the split is. If you're going to go build something for the cloud that is just cloud-native or at the cloud level, Go is a language you want to do that in.

I would say Go is a systems language, but it is more of a cloud systems language than a low-level systems language. I think that's where the split is. If you're going to go build something for the cloud that is just cloud-native or at the cloud level, Go is a language you want to do that in.

If you want to go lower and be close to the hardware, I think that's where Zig and Rust and these other languages fit much better. because they, you know, they have that closer integration with C. They have that closer connection to the hardware. They have much more control over memory. They aren't as they aren't trying to protect you in the same ways that Go is trying to protect you.

If you want to go lower and be close to the hardware, I think that's where Zig and Rust and these other languages fit much better. because they, you know, they have that closer integration with C. They have that closer connection to the hardware. They have much more control over memory. They aren't as they aren't trying to protect you in the same ways that Go is trying to protect you.

So I think that Go is still a very good systems language, but it's just like a higher level systems than I think what people have traditionally thought. And I think people have in the past just kind of bucketed all of systems together. I think we're starting to see that they're they're splitting apart.

So I think that Go is still a very good systems language, but it's just like a higher level systems than I think what people have traditionally thought. And I think people have in the past just kind of bucketed all of systems together. I think we're starting to see that they're they're splitting apart.

They're becoming more nuanced, more bifurcated in what they are and the languages are separating into the different parts of that to serve those communities.

They're becoming more nuanced, more bifurcated in what they are and the languages are separating into the different parts of that to serve those communities.

I don't think so. I think that the separation is more about, I think, first of all, who is your target audience? I think for Go, the target audience is, we want to make sure that the super experienced programmers and engineers can write good, efficient code. But we want to make sure that average programmers can also just pick this up and run with it, can go implement things.

I don't think so. I think that the separation is more about, I think, first of all, who is your target audience? I think for Go, the target audience is, we want to make sure that the super experienced programmers and engineers can write good, efficient code. But we want to make sure that average programmers can also just pick this up and run with it, can go implement things.