nerves VS gokrazy

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.

Switching to gokrazy[0] was the best thing I did for my Raspberry Pi uptimes. I think a lot of that is because it defaults to using read-only partitions so the common issue of SD cards falling over when you run apt upgrade no longer happens.

But I also think that gokrazy's simplicity and design helps it be just a solid, reliable foundation to build on top of.

[0]: https://gokrazy.org/

The idea there sounds a lot like https://gokrazy.org/, which builds a minimal go userland, wrapping one or more user provided go applications, and bundles in a linux kernel.

Targets mostly at single board computers, and I think it downloads pre-built kernels (and bootloaters if needed), rather than trying to build them directly, since getting a working cross compilation toolchain set up and plumbed into the kernel compilation process is still a pain.

I've personally only used yocto/open-embedded for that which does nicely handle building the cross-compilation toolchain, kernel image, and modules. But it is kinda overkill for that task, being designed to build a whole userland too.

reminds me of https://github.com/gokrazy/gokrazy which does similar things.

https://gokrazy.org/ would like a word

Fun! We have support for running on gokrazy (https://gokrazy.org/) already, and that's probably where Unikernel Linux is more applicable for us, for when people just want a "Tailscale appliance" image.

I'll email you.

gokrazy exists! https://github.com/gokrazy/gokrazy

https://github.com/gokrazy/gokrazy for one example