Julius Gustavsson

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.

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.

Yeah, that was definitely the case.

Yeah, that was definitely the case.

Yeah, that was definitely the case.

Yeah, absolutely. Well, needless to say, then maybe we'll come to that later on how we came to the LPA project, but where we're not using it, at least not yet.

Yeah, absolutely. Well, needless to say, then maybe we'll come to that later on how we came to the LPA project, but where we're not using it, at least not yet.

Yeah, absolutely. Well, needless to say, then maybe we'll come to that later on how we came to the LPA project, but where we're not using it, at least not yet.

But yeah, I'd done a fair bit of... And also a lot of embedded systems are callback-driven in their nature because you're getting all kinds of events from hardware peripherals, from other things, then your main thread constantly and also your... When you're achieving something, you usually need to do it in steps.

But yeah, I'd done a fair bit of... And also a lot of embedded systems are callback-driven in their nature because you're getting all kinds of events from hardware peripherals, from other things, then your main thread constantly and also your... When you're achieving something, you usually need to do it in steps.

But yeah, I'd done a fair bit of... And also a lot of embedded systems are callback-driven in their nature because you're getting all kinds of events from hardware peripherals, from other things, then your main thread constantly and also your... When you're achieving something, you usually need to do it in steps.

So you do something, register a callback, wait for that callback to be called, then you continue. And even in that stage of futures at the time, it was still removing a lot of boilerplate already then. So that's why I thought it was intriguing.

So you do something, register a callback, wait for that callback to be called, then you continue. And even in that stage of futures at the time, it was still removing a lot of boilerplate already then. So that's why I thought it was intriguing.

So you do something, register a callback, wait for that callback to be called, then you continue. And even in that stage of futures at the time, it was still removing a lot of boilerplate already then. So that's why I thought it was intriguing.

It's a good question. I guess I would most likely use some sort of async framework in C++, I guess, since we had gRPC, and gRPC, protobuf, all that stuff was already fairly well supported in C++, so I guess I would go for that. And I don't remember how... if those async frameworks at that time in C++ were, how far they'd come. They probably had similar sort of features.

It's a good question. I guess I would most likely use some sort of async framework in C++, I guess, since we had gRPC, and gRPC, protobuf, all that stuff was already fairly well supported in C++, so I guess I would go for that. And I don't remember how... if those async frameworks at that time in C++ were, how far they'd come. They probably had similar sort of features.

It's a good question. I guess I would most likely use some sort of async framework in C++, I guess, since we had gRPC, and gRPC, protobuf, all that stuff was already fairly well supported in C++, so I guess I would go for that. And I don't remember how... if those async frameworks at that time in C++ were, how far they'd come. They probably had similar sort of features.

The problem there is that you usually don't... When the closure that you register actually gets called, you're basically on your own because the... There are all sorts of assumptions that need to be upheld for that to actually work properly.

The problem there is that you usually don't... When the closure that you register actually gets called, you're basically on your own because the... There are all sorts of assumptions that need to be upheld for that to actually work properly.

The problem there is that you usually don't... When the closure that you register actually gets called, you're basically on your own because the... There are all sorts of assumptions that need to be upheld for that to actually work properly.