I think the concern is about "lean". I don't think there's a lot of code yet, but I do see it will use http://u-root.tk/.
When there is a build system, you'll be able to choose whatever initramfs you want to implement your boot policies. The two choices we have today are NERF (= LinuxBoot + u-root as initramfs, as you linked) and Heads (LinuxBoot with Heads kernel and runtime, see http://osresearch.net).
Heh, that gave me a chuckle
> Userland written in Go (http://u-root.tk)
So much for Go not being a systems programming language.
There are other examples already.
Fuchsia TCP/IP stack and file system driver management utilities are implemented in Go.
https://groups.google.com/d/msg/golang-dev/2xuYHcP0Fdc/tKb1P...
Android's new GPU debugger is written in Go.
https://github.com/google/gapid
An then there are some bare-metal experiments like G.E.R.T.
(I was going for a tongue-in-cheek ribbing of the Go-haters - in retrospect my wording sounds a bit passive-aggressive, probably should have ended with an exclamation mark and a smily or something)
I love it is based on a mix of Oberon and Limbo, compiled to native code and an improvement for what a safe C like language should probably look like, and who knows maybe someone decides a day to do a "Goberon" OS for they OS PhD research.
Basically what Java and C# 1.0 should have been all along, about 20 years ago.
However I also dislike some of the design decisions regarding features that will never come to Go, regardless of how much we get to discuss them, even with the mirage of Go 2.0.
https://schd.ws/hosted_files/osseu17/84/Replace%20UEFI%20wit...
(The video of the presentation is linked in the OP).
There's already two and a half obscure OS's running underneath the OS for booting. So this replaces all that crap with something lean and good.