posix_spawn is a wrapper around fork/do some setup/exec which is the most common way fork is used. Also, fork is normally implemented as a wrapper around clone

posix_spawn is a wrapper around fork/do some setup/exec which is the most common way fork is used. Also, fork is normally implemented as a wrapper around clone FWIW. > I don't think he even understands the concept of programs sharing an address space (he's also anti-thread). Personally, I find it easier to reason about than both the parent and the child having the same return stack but YMMV.