At The Jellyfish Conference

Well, there's one thing I didn't put here, and it's got an exclamation point, so I assume you're excited about working with Rust?

No, I'm more acknowledging that people will be shocked and horrified or whatever after years of explaining that I'm hoping to retire before having to use Rust.

But you recently got a Rust assignment.

Well,

the more accurate thing to say is I had no reason to use it.

So I'm looking at it.

And unfortunately, or fortunately, depending on your perspective, I now have a reason to use it.

So I'm trying to very quickly learn enough Rust to port something from... what's basically desktop Rust or whatever you want to call it to an embedded device.

And it's a series of algorithms that someone has already ported from Python.

And yeah, and I would like to not have to convert that to C if at all possible and just have it run in native Rust.

But there's things that need to be done to make it more embedded friendly.

And the rest of your embedded system is in C?

Yeah, it's Zephyr Project, NRF, SDK, standard stuff, all in C.

So what are the first three things you like about Rust?

That's a loaded question.

You were sure I was going to ask, what are the first three things you hate about Rust?

Three

things? I'd accept one, you know.

So

there's a lot of things in Rust that are very similar to Swift that I like.

Swift, of course, is object-oriented, has a lot of inheritance and stuff.

Rust is, as far as I can tell, not really that way.

It's more like C.

But there are kind of some nods to object-orientedness.

So you can have structs that... have functions associated with them, which basically feel like classes.