But if you pass resources and data form forked child to parent, you are already using shared memory.
And, in this case, it sounds like a thread would do exactly what you want, but without the oddities of fork().
And, in this case, it sounds like a thread would do exactly what you want, but without the oddities of fork().
I like the ease with which you can pass resources and data to the forked child from the parent, though. Otherwise I'd have to do a lot of serialiation and deserialization, or use shared memory, or unix sockets to pass fds, all of which also has it's gotchas and is way more complicated and error prone.