I miss working with Erlang especially, but it's also certainly kind of a niche thing. Other languages are faster and have more effort being put into them.
Erlang ARM32 JIT is born
11–20 of 20 posts
Re: Erlang ARM32 JIT is born
#12I don't have any experience with ARM, but from what I've seen people write, isn't 32-bit ARM discontinued after v7?
There's still a huge embedded market! Plenty of microcontrollers have a single-digit number of Cortex-M cores and memory/flash counted in the megabytes. It'll be decades until that market reaches the multi-gigabyte point, so why bother wasting a whole bunch of memory on 64-bit pointers? I'm not quite sure why you'd want to run Erlang on it, but the hardware exists.
Erlang is invented before IoT was a thing to facilitate distributed computing for telecommunication in a highly reliable manner. It makes perfect sense to adapt it for driving fleets of cheap IoT devices.
Re: Erlang ARM32 JIT is born
#13A Tcl article and an Erlang article - good morning! I miss working with Erlang especially, but it's also certainly kind of a niche thing. Other languages are faster and have more effort being put into them.
Re: Erlang ARM32 JIT is born
#14Gah, misread that as esp32 JIT, which would be eye opening!
esp32 is now also RISC-V so I guess it wouldn't be completely out of the question. But I guess you meant this flavor https://www.cadence.com/content/dam/cadence-www/global/en_US...
Re: Erlang ARM32 JIT is born
#15A Tcl article and an Erlang article - good morning! I miss working with Erlang especially, but it's also certainly kind of a niche thing. Other languages are faster and have more effort being put into them.
Re: Erlang ARM32 JIT is born
#16I don't have any experience with ARM, but from what I've seen people write, isn't 32-bit ARM discontinued after v7?
There's still a huge embedded market! Plenty of microcontrollers have a single-digit number of Cortex-M cores and memory/flash counted in the megabytes. It'll be decades until that market reaches the multi-gigabyte point, so why bother wasting a whole bunch of memory on 64-bit pointers? I'm not quite sure why you'd want to run Erlang on it, but the hardware exists.
https://nerves-project.org/#features has a decent pitch for why. (Most of the features listed here aren't features of Nerves-the-Elixir-IoT-runtime-codebase per se, but rather benefits of Nerves-the-toolchain enabling you to easily build lean, embedded Erlang [on Linux] firmware images.)
Re: Erlang ARM32 JIT is born
#17I don't have any experience with ARM, but from what I've seen people write, isn't 32-bit ARM discontinued after v7?
Re: Erlang ARM32 JIT is born
#18A Tcl article and an Erlang article - good morning! I miss working with Erlang especially, but it's also certainly kind of a niche thing. Other languages are faster and have more effort being put into them.
Re: Erlang ARM32 JIT is born
#19I don't have any experience with ARM, but from what I've seen people write, isn't 32-bit ARM discontinued after v7?
Their motivation is explained in the first post of the series[1] [1] https://www.grisp.org/blog/posts/2025-06-23-jit-arm32.1#why-...
Their existing hardware is aarch32. It really is that simple.
Re: Erlang ARM32 JIT is born
#20I don't have any experience with ARM, but from what I've seen people write, isn't 32-bit ARM discontinued after v7?
Their motivation is explained in the first post of the series[1] [1] https://www.grisp.org/blog/posts/2025-06-23-jit-arm32.1#why-...