Matthias Endler
👤 PersonAppearances Over Time
Podcast Appearances
And you still saw the potential there, even though it was a bit, let's say, half-baked or it wasn't completely fleshed out yet?
Given your background as a C developer and probably also as someone who has a fair share of experience with embedded systems, how would you have done that with the technologies that you used before? C, how would that look like?
Given your background as a C developer and probably also as someone who has a fair share of experience with embedded systems, how would you have done that with the technologies that you used before? C, how would that look like?
Given your background as a C developer and probably also as someone who has a fair share of experience with embedded systems, how would you have done that with the technologies that you used before? C, how would that look like?
For instance, which assumptions?
For instance, which assumptions?
For instance, which assumptions?
Even for someone like you who has quite a ton of experience in that area?
Even for someone like you who has quite a ton of experience in that area?
Even for someone like you who has quite a ton of experience in that area?
So for some context, we are in 2018-ish and you built your first hardware abstraction layer for controlling the fans from Android. And you saw it working on first try. That must have made you pretty excited about Rust and its potential to go from idea to first prototype layer. in a reliable manner. Did you show that prototype to other colleagues?
So for some context, we are in 2018-ish and you built your first hardware abstraction layer for controlling the fans from Android. And you saw it working on first try. That must have made you pretty excited about Rust and its potential to go from idea to first prototype layer. in a reliable manner. Did you show that prototype to other colleagues?
So for some context, we are in 2018-ish and you built your first hardware abstraction layer for controlling the fans from Android. And you saw it working on first try. That must have made you pretty excited about Rust and its potential to go from idea to first prototype layer. in a reliable manner. Did you show that prototype to other colleagues?
Did you talk about Rust back in the day, or was it more of a hobby and side project?
Did you talk about Rust back in the day, or was it more of a hobby and side project?
Did you talk about Rust back in the day, or was it more of a hobby and side project?
I'm trying to put myself into the position of a team member or a colleague of yours in 2018. So you're telling me about Rust. You're enthusiastic about it. I see the prototype. I see that it's working. But I don't really know. I don't really have any Rust experience. And I don't know how long it took to build that prototype.
I'm trying to put myself into the position of a team member or a colleague of yours in 2018. So you're telling me about Rust. You're enthusiastic about it. I see the prototype. I see that it's working. But I don't really know. I don't really have any Rust experience. And I don't know how long it took to build that prototype.
I'm trying to put myself into the position of a team member or a colleague of yours in 2018. So you're telling me about Rust. You're enthusiastic about it. I see the prototype. I see that it's working. But I don't really know. I don't really have any Rust experience. And I don't know how long it took to build that prototype.
So I look at all of the tooling that we built in C and C++ and the ecosystem that requires... And then I ask you about QNX support or tricore support for Infineon CPUs. And you say, well, it doesn't exist or it's a work in progress. Suffice to say, I'd be a little skeptical.