3 ms·
It's great to hear interest in this area - the more places I can run Erlang/Elixir, the more likely I am to use it even in the places it can traditionally run (
by rkangel 8y ago
It's great to hear interest in this area - the more places I can run Erlang/Elixir, the more likely I am to use it even in the places it can traditionally run (it's a more useful language to me if I can use the same codebase everywhere).
If you are looking to make an embedded focused VM, obviously ARM is the most useful target to run on.
- kvakvs 8y agoBy using C++ and Rust obviously ARM was on my mind, and I have plenty of test boards ranging from 192kb to hundreds MB of RAM to experiment with. It just never reached that stage. The two main ideas were to be different implementation for large machines (ErlangRT) or to be small (E4VM and gluonvm1).
- rubyn00bie 8y agoIs there a platform the BEAM doesn't currently target? I'm not aware of anything that isn't completely esoteric... You can run it on ARM currently. BEAM has been in use for over 20 years in telephone systems running on insanely old and bizarre hardware. Is there a platform you have in mind besides ARM?
- baobrien 8y agoI could be wrong, but I don't think BEAM really runs on microcontrollers. Erlang might be a good environment on the same sorts of micros (32 bit, dozens of KB of ram) MicroPython targets.
- marci 8y agohttps://github.com/bettio/AtomVM https://github.com/bettio/AtomVM edit: it's a work in progress, but it's a start. Looks like the author is actively working on it.
- kvakvs 8y agoIt is memory not CPU that is the main limitation. Under 20MB RAM you are entering a gray zone, where BEAM barely runs. You can keep removing modules from the standard library and optimising it fit into maybe 8MB RAM (as project GRISP did) but smaller than that BEAM VM would not even boot to shell.