Hacker News Reader

> C should have never ben part of Go to begin with

It’s unavoidable on most platforms. Linux is pretty much the only mainstream platform where the syscall interface is considered the stable interface between user and kernel. Other platforms (like macOS, *BSD, and Windows) consider libc (or equivalent in Win32) to be the stable interface.

Win32 in particular is known for guzzling KBs of stack before getting around to making an actual syscall, so you wouldn’t be able to avoid trampolining through an ABI-compatible environment anyway.

This is a must read for you then if you don't understand the role C plays in modern operating systems: https://faultlore.com/blah/c-isnt-a-language/

Unless you want to rebuild the entire world, including the operating system, Go will have to touch the C FFI boundary at some point.