Comment by throw2022110401
2 years ago
For language runtimes that don't normally have to deal with C baggage having to drag libc into your address space and going through libc code for syscalls makes this a less secure platform.
2 years ago
For language runtimes that don't normally have to deal with C baggage having to drag libc into your address space and going through libc code for syscalls makes this a less secure platform.
+1.. Why not create a standard/stable syscall interface instead of pushing an anachronistic libc interface.