3 ms·
Yeah, I know go has had issues because they subvert libc themselves in similar fashion. I wonder how this will turn out.
by nullpoint420 8mo ago
Yeah, I know go has had issues because they subvert libc themselves in similar fashion. I wonder how this will turn out.
- LoganDark 8mo agoI think they had to revert back to libc on macOS/iOS because those have syscall interfaces that truly are not stable (and golang found that out the hard way). I wonder if they had to do the same on BSDs because of syscall filtering.
- samus 8mo agoIndeed, OpenBSD recently added hardening measures and started restricting the generic syscall interface to libc.
- wrs 8mo agoGo backed out of their strategy on MacOS and started using libc (libsystem?), because when Apple says something is internal and may change without notice, they really mean it. It may be a better risk with Microsoft, but it’s still a risk.
- lelanthran 8mo agoSame way it turned out for Go: they had to walk it back.