3 ms·
> The problem is that on microcontrollers everything is compiled, linked, and deployed together using really old-fashioned tools. Not necessarily. There are m
by the__alchemist 5y ago
> The problem is that on microcontrollers everything is compiled, linked, and deployed together using really old-fashioned tools.
Not necessarily. There are modern and pleasant workflows using Rust.
This article is somewhat general. Ie, what is his intended use case? What is he building? Part of the beauty of embedded programming is you can avoid the complications of abstractions like virtual machines and operating systems, and the performance penalties that accompany them.
- ashtonkem 5y agoAlso, there are a variety of interpreted language environments for microcontrollers, including at least one in Python and one in lisp. Saying that microcontrollers must used statically compiled code is objectively incorrect. Now most projects will use C due to space issues, but that’s a different argument.
- sjburt 5y agoMost projects use C because there was zero consideration for anything else. No embedded team sits down at the beginning of the project and says "should we use lisp?". It's just C. Or maybe "C, but use a C++ compiler with less UB".
- pjmlp 5y agoIndeed, if one moves into maker community there have been Basic, Pascal, Oberon, Java compilers for ages. Those companies manage to stay in business selling such compilers for at least three decades now, which kind of proves there is a market of people willing to pay for them, instead of going with C like everyone else.
- markdeloura 5y agoCircuitPython (derived from MicroPython) is objectively pretty excellent, and running on an increasing number of platforms. It's been a really great platform for education.