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.

It's also a good way to learn about UEFI for people most familiar with go.

Quite apart from that, an EFI shell that's less awful than the standard UEFI one is an interesting project in its own right...

I've been idly following this stuff on & off for years, but I never saw proving a point "instead of using Rust" as one of the motivations of the project. Was that ever stated anywhere?

That's a shame, I was hoping it would be so I could boot thousands of kernels in parallel at once

No amount of proven points will give Go null safety, though.

If one can't write safe C code, then maybe stick to web development and leave the bootloaders and UEFI stuff to people who can.

Training wheels are merely a race to the bottom for barely-literate programmers.