Get the latest tech news
Proposal: Add bare metal support to Go
Proposal Details I propose the addition of a new GOOS target, such as GOOS=none, to allow Go runtime execution under specific application defined exit functions, rather than arbitrary OS syscalls, ...
This also allowed us to implemented execution under UEFI which enabled 100% Go EFI applications and bootloaders such as go-boot(which currently booted Linux on the Thinkpad I am writing from). The only component that is somewhat low-level and sensitive in terms of maintenance between major Go releases is our asynchronous goroutine waking function, which is used to serve external interrupt requests. However such function can be re-implemented in a manner consistent with existing OS signaling or, simply with the awareness and inclusion of GOOS=none, hooked to a much simpler standardized interface within the timer structure, which so far has not been implemented purely to avoid any pollution with non-tamago architectures.
Or read this on Hacker News