Comment by megous
7 years ago
> Of course, all Windows APIs are terrible, but that doesn't make complaints about fork() any less legitimate. The concept of Establishing empty processes, instead of cloning yourself, is much more sane.
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.
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().
The memory is not shared, but copied, so you don't have to care about concurrent memory access.