3 ms·
It's interesting the timing on this rename to Zircon going through and the Fuchsia team attempt to get Fuchsia support into Go[0]. EDIT: sounds like the rename
by kyrra 9y ago
It's interesting the timing on this rename to Zircon going through and the Fuchsia team attempt to get Fuchsia support into Go[0].
EDIT: sounds like the rename was in the works for a while and the Go port was just holding off until it completed:
> "this change has been a few months in the works..." "...I delayed this email until it was almost done."
[0] https://groups.google.com/forum/#!topic/golang-dev/2xuYHcP0Fdc https://groups.google.com/forum/#!topic/golang-dev/2xuYHcP0F...
- rajathagasthya 9y agoThat's where I got the link for Zircon :) I thought about posting the Go discussion initially which is really interesting on its own.
- pjmlp 9y agoThanks for the link. > In particular, the network stack is implemented Go, so for any program to make a TCP connection on Fuchsia, we need the Go port to be working: It looks like systems programming to me. :)
- puzzle 9y agoSpeaking of unconventional system stuff in Go, Google has a Linux boot FS, which, instead of featuring the usual BusyBox, ships with an init, the Go toolchain and a source tree. The /bin replacements are symlinks as expected, but the twist is that they point to a binary that is compiled on first boot. http://u-root.tk/ http://u-root.tk/
- sanxiyn 9y agoThis reminds me of TCCBOOT.
- mastax 9y ago> The fuchsia kernel is running on GCE, with support for network and disk coming very soon. That's how I intend to run builders for build.golang.org. Wow!