biscuit

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

You might like Biscuit: https://github.com/mit-pdos/biscuit It was specifically written to measure the performance overhead of a high-level language in kernel, so it explicitly makes the same design choices as Linux: monolithic, POSIX-compatible. Results look pretty good.

> kernel developers do not allow third party runtimes in the kernel. Even meager Rust's "panic" runtime is a contentious Much in Linux is contentious :-) which is why the module system is nice. A kernel module for C code requires no permission from Linux-core unless you need it distributed with the kernel (which, yes, might be required for "credibility" - but critically also might not). It may require many decls to access various kernel APIs, but those can be (semi-)automated or just done as-needed. So, Linux kernel policy is not so relevant (at best) which is what I meant by "no special support" (admittedly brief). Kernel coding is always a bit trickier, and you may need to build up some support code to make integration nice, though as well as decl generators (though none of that need be distributed "with Linux"). > Can one disable r

No, it isn't the third release of a POSIX like OS research written in Go, https://github.com/mit-pdos/biscuit

Go has been used to implement OS kernel code, e.g. in the Biscuit OS from MIT: https://github.com/mit-pdos/biscuit Of course, the garbage collector did not exactly make it easier - but it's an interesting piece of software.

Go team only changed their message due to the pitch forks they were getting from the UNIX/C crowd. There are people that believe systems programming languages in an OS kernel is doable with some form of GC, and then there those that will never change their mind. https://www.f-secure.com/en/consulting/foundry/usb-armory https://blog.arduino.cc/2019/08/23/tinygo-on-arduino/ https://gvisor.dev/ https://github.com/mit-pdos/biscuit https://github.com/ycoroneos/G.E.R.T By the way, NeXTSTEP drivers were written in Objective-C, and the new userspace framework, DriverKit, is an homage to the NeXTSTEP driver API. https://www.nextop.de/NeXTstep_3.3_Developer_Documentation/O...

Here's a POSIX kernel in Go, written explicitly to prove your point wrong: https://github.com/mit-pdos/biscuit https://pdos.csail.mit.edu/projects/biscuit.html

Eh... https://github.com/mit-pdos/biscuit

Off topic but it's quite interesting to see that on HN, a great amount of the comments of a GO post talk about Rust, and vice versa. As a system guy, I am also happy to follow two OS projects in these two: [1] https://github.com/mit-pdos/biscuit [2] https://github.com/redox-os/redox

Let's not forget the Biscuit operating system by MIT just recently published at OSDI'18: - The paper: https://pdos.csail.mit.edu/papers/biscuit.pdf - The code: https://github.com/mit-pdos/biscuit

People are doing OS research in Go, and Fuchsia core components like the TCP/IP stack are written in it, regardless of what the HN crowd thinks where Go should be used. https://github.com/mit-pdos/biscuit https://github.com/ycoroneos/G.E.R.T Last version of Plan 9 was actually Inferno, which HNers keep forgetting about, which used Limbo for userspace code. Limbo uses the channel syntax later adopted by Go.