Hacker News new | ask | show | jobs
by vvanders 3422 days ago
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.
3 comments
mseepgood 3422 days ago
> 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.

link
nickpsecurity 3422 days ago
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.
link
pjmlp 3422 days ago
As mseepgood already replied, you can do that in Go.
link