New comment by univspl in "Fork() is evil; vfork() is goodness; afork() would be better; clone() is stupid"

univspl — Mon, 28 Feb 2022 18:49:26 +0000

To me this feels like a call for more powerful language primitives. i.e. a way to specify some action to take to "set up" the child process that's more explicit and readable than one special behaving in a particularly odd way. I'm imagining closures with some kind of Rust-like move semantics, but not entirely sure.

(if we're speaking in terms of greenfield implementation of OS features)

Hacker News: univspl

New comment by univspl in "Fork() is evil; vfork() is goodness; afork() would be better; clone() is stupid"