I like js, but I won't sacrifice all the performance aspects in the sole name of productivity.
Node(nor any GC lang) is simply not designed for embedded dev. I'll gladly switch to C or Rust that are designed for this kind of work.
Node(nor any GC lang) is simply not designed for embedded dev. I'll gladly switch to C or Rust that are designed for this kind of work.
How would you differentiate them from today's embedded devices? ;)
Amstrad PCW 1512 vs ESP32.
If I could use high languages in MS-DOS when performance wasn't critical enough to warrant being written in Assembly, so can we in our modern embedded devices.
The exception being micro-controllers like PICs.
Intent and usage type. Minicomputers were still "general-purpose" computers, expected to run varying user code while embedded devices are more or less fixed-function.
From a more technical perspective, one difference is the expectation of (hard) real time control. While I have no doubt that some genius has put PDP-11 into industrial process control loop or something, generally UNIX (and C by extension) was not designed for real-time applications
But yeah, those weren't running UNIX for the most part, but probably RT-11 if their developers were sane.
http://www.astrobe.com/default.htm
https://www.wildernesslabs.co/
https://www.ptc.com/en/products/developer-tools/perc
http://www.microej.com/portfolio-item/28-kbyte-java-virtual-...
Genereally speaking embedded devices is a very broad area, from a tiny PIC up to a couple of MBs.
There are many factors at play and in many cases it is actually worthwhile to spend 5€ more per unit and get a better development experience.
It is a decision per case basis and not really something that we can generalise as all embedded development is like X.