Hacker News Reader

Comment by bacongobbler | Hacker News Reader

I believe this is why you are getting downvoted:

> It's not going to be displacing low-level programming any time soon, unless radical changes are in store for 2.x and beyond, hypothetically

What radical changes are you referring to, and why are they needed in order for Go to be a de-facto language for system programmers?

View on HN

Drop the garbage collector. Systems programming cannot stop the world.

You can already do that: http://golang.org/pkg/runtime/

That's not useful for a kernel. You can disable garbage collection in go, but go doesn't provide the tools to disable creating garbage entirely. You can get really close to creating zero garbage through profiling and helping the compiler's escape analysis, but afaik the go spec makes no guarantees about stack vs heap allocation.

> That's not useful for a kernel.

Oberon Kernel.Mod, initial version 11.4.86

http://www.inf.ethz.ch/personal/wirth/ProjectOberon/Sources/...

I failed to see any references to the go runtime package in that link which leads me to believe you misunderstood my statement. Using the APIs documented in the go runtime package to disable garbage collection would not be an effective memory management strategy for a kernel.

The GC is more of a cultural issue than anything (what with Oberon being perfectly fine), but it will have an impact as a result. The runtime will be an overhead, though it does have a malleable library interface, apparently.

Reply on news.ycombinator.com