Julius Gustavsson

using futures and and and back then there was no async await so this was like yeah uh futures zero zero point one or yeah and and it was it was such an amazing experience because yeah you know you had to do all these things to get everything to work because there was so many moving parts to get like the things to build in the build system and and yeah getting the whole like

from the button to the actual methods being called in the HAL and then having that send out something over gRPC, over Wi-Fi to that other chip. And basically when I had it all wired up and it started to build, it took me a while, the fans just turned on on the first try. So it's just super amazing. I had never experienced that before.

from the button to the actual methods being called in the HAL and then having that send out something over gRPC, over Wi-Fi to that other chip. And basically when I had it all wired up and it started to build, it took me a while, the fans just turned on on the first try. So it's just super amazing. I had never experienced that before.

from the button to the actual methods being called in the HAL and then having that send out something over gRPC, over Wi-Fi to that other chip. And basically when I had it all wired up and it started to build, it took me a while, the fans just turned on on the first try. So it's just super amazing. I had never experienced that before.

And so that was like a first proof point that this is definitely something.

And so that was like a first proof point that this is definitely something.

And so that was like a first proof point that this is definitely something.

I would say, of course, my experience didn't hurt. But I know for a fact I've been doing C and C++ for mostly C though, but a fair bit of C++ as well for the better part of 20 years. And every single time there is always something, or at least something creeps up. Especially when you're least expecting it.

I would say, of course, my experience didn't hurt. But I know for a fact I've been doing C and C++ for mostly C though, but a fair bit of C++ as well for the better part of 20 years. And every single time there is always something, or at least something creeps up. Especially when you're least expecting it.

I would say, of course, my experience didn't hurt. But I know for a fact I've been doing C and C++ for mostly C though, but a fair bit of C++ as well for the better part of 20 years. And every single time there is always something, or at least something creeps up. Especially when you're least expecting it.

There's something that you didn't think about, or someone else didn't think about, or something you thought of that wasn't written down, and then someone else broke that assumption. There's always something that... that makes these kind of, especially when it's so many moving parts in this little proof of concept that I was doing there, that, yeah, that just wouldn't have happened.

There's something that you didn't think about, or someone else didn't think about, or something you thought of that wasn't written down, and then someone else broke that assumption. There's always something that... that makes these kind of, especially when it's so many moving parts in this little proof of concept that I was doing there, that, yeah, that just wouldn't have happened.

There's something that you didn't think about, or someone else didn't think about, or something you thought of that wasn't written down, and then someone else broke that assumption. There's always something that... that makes these kind of, especially when it's so many moving parts in this little proof of concept that I was doing there, that, yeah, that just wouldn't have happened.

Or at least not for me, that's for sure. So yeah, Rust definitely did the heavy lifting there, or at least made sure that I had, because Rust tends to make you think through the whole design up front, basically, or at least, you know, a much larger part. So, yeah, so there are these fine, you know, loose ends that you also need to tie up before it actually builds and runs.

Or at least not for me, that's for sure. So yeah, Rust definitely did the heavy lifting there, or at least made sure that I had, because Rust tends to make you think through the whole design up front, basically, or at least, you know, a much larger part. So, yeah, so there are these fine, you know, loose ends that you also need to tie up before it actually builds and runs.

Or at least not for me, that's for sure. So yeah, Rust definitely did the heavy lifting there, or at least made sure that I had, because Rust tends to make you think through the whole design up front, basically, or at least, you know, a much larger part. So, yeah, so there are these fine, you know, loose ends that you also need to tie up before it actually builds and runs.

And I think that those are the things that make the difference.

And I think that those are the things that make the difference.

And I think that those are the things that make the difference.

Probably, but the nature of the, since we were doing like gRPC communication over Wi-Fi, it was very asynchronous in its nature. So I wanted to try it out and see how it would work. So yeah, that was the idea.