Conversation

So crazy it might work: I do a lot of #ulisp on ESP32 MCUs. The MCUs interoperate with an SBC...where I'm writing in #Lisp (I share common code w/ the MCU). Learning CL is a bridge too far for my team, so what if I restrict my CL code to the ulisp subset?

Replying to

I found this to be a brick wall in many cases. Same for Haskell, Erlang, Forth, anything not C/C++ basically. My approach has been to use C for code that others need to touch during debugging or to make small changes, then go all in on the meta system (tests, lib code gen).

Replying to

and

Though I am finally getting some love towards Rust in my current project. Things are changing in that direction...

12:56 PM · Aug 7, 2022Twitter Web App

Replying to

and

Rule of thumb: most embedded software engineers do not care about learning yet another language.

Replying to

Luckily, these aren't embedded software engineers and most will just need to be my "backup" for code maintenance (i.e. me hit by a bus). I get to choose the languages and exert my evil influence ;)