4 ms·
Embedded is a very barren environment. One where bytes of memory and individual clock cycles can matter a lot. This is just not the environment a memory manage
by Alupis 4y ago
Embedded is a very barren environment. One where bytes of memory and individual clock cycles can matter a lot.
This is just not the environment a memory managed language, running atop a virtual machine runtime is suitable for. You'd have to strip all that away, and then you'd just be left with C# syntax, but it would be very far from being C# and would not be compatible with any standard C# library, framework or platform.
For a lot of embedded work, even Rust is having a difficult time getting traction. Even the C++ Standard Library doesn't fit on many of the systems folks are working on, let alone the STL.
- HeyLaughingBoy 4y agoThere's embedded and then there's embedded. The system I'm working on at my day job has about 1meg of Flash and, IIRC, 128k RAM. It was reduced in resources to save cost (disposable device). The one I'm working on at home has about 4M Flash and 256k RAM. One of them is making liberal use of the STL and I know both have Python implementations available. Tiny, memory constrained devices are still around, but they're a smaller and smaller part of the pie every year.
- kaba0 4y agoYou do realize Java was literally made for set top-boxes and the like? Sure, there are much more resource-constrained embedded devices as well, but byte code takes up much less space than machine code, plus a naive interpreter can be really really small, so it’s not an unworkable path.