3 ms·

I'm more or less in the same professional spot as you. Responding to your criticism of Rust all I can say is that you can only convince yourself, try it, if it

I'm more or less in the same professional spot as you. Responding to your criticism of Rust all I can say is that you can only convince yourself, try it, if it isn't rhetoric you're interested in. Suddenly your code, when it runs, is bug free. It's a magic experience. More importantly it gives the ecosystem superpowers. That's an indirect response to your: > If there is a bug, it might be hard to find, but that's it. Which is damning. But typical of embedded. It's such a C shit hole. We debug most of our time, many of the tools are crappy. So you perhaps constrained yourself to 32-bit ARM devices, isolated yourself as much as you could, and created your own comfort zone? That's a symptom. There are many advantages to Rust, that run from things as basic as assuring code runs the same on a 8-bit MCU as it does on a 64-bit PC, to the trust one can have in the ecosystem, and the hive mind behind it. That said, though I see Rust becoming inevitable because of these reasons, I would very much like Zig to succeed, as it uniquely has the flexibility to construct the optimal solutions embedded craves for. Rust is more rigid in that sense, so Zig appeals more to the creative of minds.

scoutt 4y ago
I'm not so critical of the language itself (it's just another language), but how it's managed and promoted. I'm also critical about some of it evangelists. For example, from your comment I can learn I work in (or with?) a C shithole, that I don't want to try Rust (which I am learning, at my own slow pace) and that I don't want to use Rust because I have a confort zone, and "a symptom". Tell me, how on earth I am going to be motivated to learn Rust, by reading something like that? > We debug most of our time I can't remember the last time I chased a memory bug of some sort. On embedded, to me, debug means chasing a logical bug or an internal peripheral not working, or finding workarounds for some external peripheral that is not working or answering as it should. So it really feels bad when I read the following sentence: "is bug free. It's a magic experience" What are you talking about? Perhaps free from "memory bugs"? As I said, I rarely deal with memory bugs. > your own comfort zone I develop and maintain 8, 16 and 32 bit projects, from Cortex-M down to MSP430/STM8. Also I'm in charge of embedded Linux and Android customization and builds, 32 and 64 bits (former Windows CE developer). I wish I had a comfort zone... sometimes.

scoutt 4y ago

I'm not so critical of the language itself (it's just another language), but how it's managed and promoted. I'm also critical about some of it evangelists. For example, from your comment I can learn I work in (or with?) a C shithole, that I don't want to try Rust (which I am learning, at my own slow pace) and that I don't want to use Rust because I have a confort zone, and "a symptom". Tell me, how on earth I am going to be motivated to learn Rust, by reading something like that? > We debug most of our time I can't remember the last time I chased a memory bug of some sort. On embedded, to me, debug means chasing a logical bug or an internal peripheral not working, or finding workarounds for some external peripheral that is not working or answering as it should. So it really feels bad when I read the following sentence: "is bug free. It's a magic experience" What are you talking about? Perhaps free from "memory bugs"? As I said, I rarely deal with memory bugs. > your own comfort zone I develop and maintain 8, 16 and 32 bit projects, from Cortex-M down to MSP430/STM8. Also I'm in charge of embedded Linux and Android customization and builds, 32 and 64 bits (former Windows CE developer). I wish I had a comfort zone... sometimes.