> Calling into system calls in libc is not a hindrance at all for the use of other languages, any more than calling directly into a syscall would be. I would s

> Calling into system calls in libc is not a hindrance at all for the use of other languages, any more than calling directly into a syscall would be. I would say that it is a hindrance though. It's a hindrance even for relatively straight forward C code. You cannot for example use clone and expect the libc to continue working. https://sourceware.org/bugzilla/show_bug.cgi?id=10311 https://sourceware.org/bugzilla/show_bug.cgi?id=10311 > If you use clone() you're on your own. These libraries are the problem, not the solution. They're full of static global data which will get clobbered whenever you do anything more complicated than I/O. They use thread local variables for returning errors codes. It's bad legacy stuff.