3 ms·
The problem go has is that there’s a rather large overhead for calling C functions [1]. So they did not switch to calling libc as far as I know. And yes the nex
by legulere 9y ago
The problem go has is that there’s a rather large overhead for calling C functions [1]. So they did not switch to calling libc as far as I know. And yes the next time Apple changes the syscalls, it will break again.
[1]: https://groups.google.com/forum/m/#!topic/golang-nuts/RTtMsgZi88Q https://groups.google.com/forum/m/#!topic/golang-nuts/RTtMsg...
- int_19h 9y agoWow. So, basically, Go is a rather insular ecosystem - since you're paying the overhead of a context switch for every single FFI call - and if you use the stock APIs, it's essentially broken by design on macOS (since it uses APIs that Apple itself does not consider stable). That's really sad. I was just beginning to like some aspects of it.