nerves VS otp

The nerves package's README.md explains what each repository is responsible for with a comprehensive listing.

You may be already aware of it, but just in case, there is the Nerves project: https://nerves-project.org/

As for embedded... I've only dabbled. Yeah you're not going to run Elixir on an Arduino or other very minimal bare metal embedded processor. But the Nerves Project (https://nerves-project.org/) which runs Elixir directly on SBCs is very well regarded. But either way it doesn't matter, since I thought we were talking about web dev, which is where Phoenix and Elixir just make more sense, for me.

For me particularly I like it for things like APIs, Web Platforms (lower resource usage than other languages), and embedded devices via Nerves. However I've also used it on my endpoints to monitor them via Erlang's built in os_mon. Another usage is the distributed nature of erlang can allow you to do things like connect two nodes and run code on a remote node via remote procedure calls. This would allow you to execute something in a nearby geolocated node and reduce latency. Fly.io did a talk on this feature.

Check out nerves, a set of tools and libraries for embedded development with Elixir.

Is this kinda like the Nerves approach but for Golang? (https://github.com/nerves-project/nerves)

Nerves is also popular for embedded.

Theoretically, you could install any version that appears in https://github.com/erlang/otp/releases. Since it is compiled and installed from source, the installation process will take some time. When you see the following message, the installation is complete.

I’m on MacOS and erlang.org, elixir-lang.org, and postgresql.org all suggest installation via Homebrew, which is a very popular package manager for MacOS.

You can read my original report and subsequent PRs in Erlang/OTP here: https://github.com/erlang/otp/issues/5811

- a massive speedup of a common static analyzer for Erlang (https://github.com/erlang/otp/pull/5997)

Funny that you should mention Erlang. Looking at the Github for Erlang, it appears that the source for Erlang is 16.8% written in C. I would bet these are not the least important bits of the whole thing. So, Erlang depends on C.

It looks more like some of the JIT improvements made it profitable to manually unroll some loops in the base64 module: https://github.com/erlang/otp/commit/a03cf1601605dee767cd9d5...

https://github.com/erlang/otp as far as I know. It's somewhat confusing and I honestly couldn't say exactly where the BEAM VM or OTP or ERTS (Erlang Runtime System) start and end. I've never dug into it. I just install Elixir and sometimes Erlang through the ASDF tool, which does all the compiling for me.