> Instead of writing firmware code in C/C++, Elk allows to develop in JavaScript. Another use case is providing customers with a secure, protected scripting environment for product customisation.
People that grew up with BASIC, z80 and 6502 Assembly and know C isn't the answer for everything.
The example with ESP32 is quite, the hardware is much more powerful than pre-Windows PCs, so why pretend it is something where C and Assembly are the only answer, when MS-DOS had plenty of languages to chose from.
> In developing this interpreter they eliminated some of the languages features to make it simpler.
That means you can't run general-purpose code safely, which means you should probably write/rewrite/adapt it, which means you might as well use a different language.
I'm a JS developer, but the parent might have a point here. Why run something like this in production when you're likely to end up in unexpected situations? Either a runtime is compliant, or you're going to have a bad time.
The project is cool, but I wouldn't use it as an example for what JS can do.
