tamago

> Write your code in Go Container not even needed, there's projects like Tamago [0] that let you run your golang application without even needing an OS [0] https://github.com/usbarmory/tamago

Im curious, have you considered using tamago instead of tinygo? https://github.com/usbarmory/tamago

The use cases is not writing unsafe C in first place, and proving the point Go is usable in such scenarios, regardless of naysayers. The creators of USB Armory also created TamaGo, instead of using Rust, exactly for the same reasons, to prove a point. https://github.com/usbarmory/tamago https://reversec.com/usb-armory/ Because in IT, seeing is believing.

Semi related: there is an active proposal of having a go OS Target of "none" (or noos (No-OS)). https://github.com/golang/go/issues/73608 Sounds like they want to maybe include https://github.com/usbarmory/tamago in the compiler.

TinyGo targets an entirely different class of systems and is not something that can be upstream being a different compiler, see https://github.com/usbarmory/tamago/wiki/Frequently-Asked-Qu...

Looks like Tamago targets multiple VM runtimes https://github.com/usbarmory/tamago?tab=readme-ov-file

Very nice overview on the whole process, congrats on what was achieved and next steps. We need more this kind of projects. Also an heads up that besides TinyGo, there is indeed another baremetal Go version available being used in commercial products, TamaGo. Although probably it would have been more challenging as TinyGo allowed for on this project. https://www.osfc.io/2024/talks/tamago-bare-metal-go-for-arm-... https://www.withsecure.com/en/solutions/innovative-security-... https://github.com/usbarmory/tamago

To be pedantic for a moment... > You can't use Go to write a kernel ... Not a production kernel, but MIT did use Go to "study the performance trade-offs of using a high-level language with garbage collection to implement a kernel" [1] There is also gVisor [2] which implements, as best as I can describe, a kernel in user space. It's intent is to intercept syscalls made in containers and to redirect its execution in a sandbox. > ... program a microcontroller ... I'm not sure if one would classify this as a microcontroller, but USB Armory did write a, iirc, Go compliant runtime for bare metal ARM and RISC-V [3]. There is also TinyGo [4] with the following listed microcontroller support [5] [1] https://github.com/mit-pdos/biscuit [2] https://gvisor.dev/ [3] https://github.com/usbarmory/tamago [4] https://tinygo.org/ [5] https://tinygo.org/doc

See TamaGo, https://github.com/usbarmory/tamago Or TinyGo, https://tinygo.org/docs/reference/microcontrollers/

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 safety 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. gVisor is a very fun project - they're really pushing the boundaries of what's possible in Go. Typical overhead is <10% thanks to a number of new features (systrap[3], directfs, in-process overlay...), all while maintaining a well-documented and super clean code base

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

If you want to go deeper, there is also bare-metal Go runtime for rpi (among others): https://github.com/f-secure-foundry/tamago

> 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