News for hackers. Stuff that matters.
Re:The State of Go by vvanders on Sunday February 05, 2017 @04:36PM (#13574782)
I never said anything about having a GC, just that if you can't poke directly at memory when you need to then you're going to have a heck of a time working on the Systems Programming space.
Re:The State of Go by mseepgood on Sunday February 05, 2017 @04:49PM (#13574841)
> if you can't poke directly at memory when you need to then you're going to have a heck of a time working on the Systems Programming space

That's possible in go with unsafe.Pointer. Go's runtime, GC and memory allocator are written in Go and make use of this.

Re:The State of Go by nickpsecurity on Sunday February 05, 2017 @09:07PM (#13576032)
Also remember Go was inspired a lot by Oberon-2. The Oberon languages were used for writing operating systems despite a GC. They just used assembly or UNSAFE constructs for stuff the type-safe or GC parts couldn't handle.
Re:The State of Go by pjmlp on Sunday February 05, 2017 @04:59PM (#13574898)
As mseepgood already replied, you can do that in Go.