> Somehow I've always found system calls far more pleasant to use than "section 3" C library interfaces I'd rather not re-write fprintf, myself, but I suppose

> Somehow I've always found system calls far more pleasant to use than "section 3" C library interfaces I'd rather not re-write fprintf, myself, but I suppose that's up to you. ;) There are some good functions implemented in the kernel instead of libc, but I personally think fork() and pthread_create() are more intuitive than learning what exactly Linux expects from a clone() system call, even assuming it's fully-documented. (Which, to be fair, it likely is. This isn't Windows; the Linux kernel API is stable and meant for public consumption.) My main point is that a kernel (as opposed to a VM) is an abstraction anyway, so I might as well pick a convenient abstraction, regardless of where the code to implement that abstraction happens to live.