nerves
tamago
| nerves | tamago | |
|---|---|---|
| 11 | 13 | |
| 2,150 | 1,277 | |
| 0.6% | 0.9% | |
| 8.4 | 8.3 | |
| 10 days ago | 8 days ago | |
| Elixir | Go | |
| Apache License 2.0 | BSD 3-clause "New" or "Revised" License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
nerves
- Embedded Elixir
-
Where Nerves-related Mix tasks are defined?
The nerves package's README.md explains what each repository is responsible for with a comprehensive listing.
- Elixir for Ruby developers: the three most important differences
-
Firefly – A new compiler and runtime for BEAM languages
You may be already aware of it, but just in case, there is the Nerves project: https://nerves-project.org/
-
Mixing sync and async views in the same application
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.
-
what is the common usage of elixir
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.
-
Functional programming language for embedded devices?
Check out nerves, a set of tools and libraries for embedded development with Elixir.
- Craft and deploy bulletproof embedded software in Elixir
-
A native Go userland for your Raspberry Pi 3 or 4 appliances
Is this kinda like the Nerves approach but for Golang? (https://github.com/nerves-project/nerves)
-
Use case of elixir
Nerves is also popular for embedded.
tamago
- Gokrazy – Go Appliances
-
OS in Go? Why Not
There's two major production-ready Go-based operating system(-ish) projects:
- Google's gVisor[1] (a re-implementation of a significant subset of the Linux syscall ABI for isolation, also mentioned in the article)
- USBArmory's Tamago[2] (a single-threaded bare-metal Go runtime for SOCs)
Both of these are security-focused with a clear trade off: sacrifice some performance for memory safe and excellent readability (and auditability). I feel like that's the sweet spot for low-level Go - projects that need memory safety but would rather trade some performance for simplicity.
[1]: https://github.com/google/gvisor
[2]: https://github.com/usbarmory/tamago
- Does Go work well as a systems language?
- Koji vam je sitan bug najviše ostao upamćen?
-
Rust 2024 the Year of Everywhere?
Of course it can, there are companies shipping products written in bare metal Go.
https://www.withsecure.com/en/solutions/innovative-security-...
https://github.com/usbarmory/tamago
-
Embedded Go finally got the first binary release
For comparison, what are the differences in goals and approach with Tamago? https://github.com/usbarmory/tamago
-
Taking a deep dive into C++ gave me more appreciation for Go's simplicity
I've been keeping an eye on TinyGo (Go compiler that targets microcontrollers and uses LLVM) and also TamaGo (allows you to run Go on bare metal, without any C dependency).
-
A native Go userland for your Raspberry Pi 3 or 4 appliances
If you want to go deeper, there is also bare-metal Go runtime for rpi (among others): https://github.com/f-secure-foundry/tamago
- TamaGo – bare metal Go for ARM SoCs
-
ISO C became unusable for operating systems development
> just proves your lack of knowledge
Tone is not needed.
For TamaGo, it seems to allow developers run their application, not build an OS on the hardware. But I have not played with it, you are right.
> TamaGo is a framework that enables compilation and execution of unencumbered Go applications on bare metal
The environment does not seem to allow building a generic operating system [1]. F-Secure ported the runtime itself to boot natively. But please correct me.
> There is no thread support
The environment you run in is specifically curated for Go applications, such as the memory layout. I'd call this an "appliance" rather than enabling Go to be used for full-fledged generic operating system implementations.
[1] https://github.com/f-secure-foundry/tamago/wiki/Internals
What are some alternatives?
libcluster - Automatic cluster formation/healing for Elixir applications
gokrazy - turn your Go program(s) into an appliance running on the Raspberry Pi 3, Pi 4, Pi Zero 2 W, or amd64 PCs!
live_svelte - Svelte inside Phoenix LiveView with seamless end-to-end reactivity
checkedc - Checked C is an extension to C that lets programmers write C code that is guaranteed by the compiler to be type-safe. The goal is to let people easily make their existing C code type-safe and eliminate entire classes of errors. Checked C does not address use-after-free errors. This repo has a wiki for Checked C, sample code, the specification, and test code.
erlexec - Execute and control OS processes from Erlang/OTP
usbarmory - USB armory - The open source compact secure computer
cubdb - Elixir embedded key/value database
go - The Go programming language with support for bare-matal programing
nerves_livebook - Develop on embedded devices with Livebook and Nerves
linux - Linux kernel source tree
hardcaml - Hardcaml is an OCaml library for designing hardware.
PyO3 - Rust bindings for the Python interpreter