June 6, 2026
Fork yeah, here we go again
Moving beyond fork() + exec()
Linux wants a faster way to open apps, but commenters are already fighting over whether anyone asked for it
TLDR: A proposed Linux feature would speed up repeatedly launching the same program, but it was rejected in its current form. Commenters immediately turned it into a bigger fight over whether this solves a real problem, whether Linux wastes memory, and whether some tools should never be separate programs in the first place.
Linux developers are once again trying to mess with one of computing’s oldest rituals: the clunky two-step where a program first makes a copy of itself, then immediately throws most of that copy away just to launch something else. A new idea called “spawn templates” promises a shortcut for apps that keep opening the same program over and over, like repeatedly calling Git in the background. In plain English: less waste, potentially more speed, fewer pointless hoops.
But the real fireworks were in the comments, where the crowd split fast between “finally, modernize this fossil” and “this is a super niche problem, please stop”. One skeptical commenter basically shrugged and said the patch being rejected was no shock at all, calling it too specialized to deserve kernel support. Another went full classic internet armchair performance rant, wondering why every Linux program seems to lug around its own copy of the same library in memory — the kind of comment that practically comes with a neon sign flashing “I may be wrong but I’m posting anyway”. Meanwhile, someone else cut through the complexity with a very relatable question: doesn’t every new process still need all the parent’s settings copied over anyway?
And then came the most deliciously blunt hot take of all: why spawn a separate program at all if the useful part should just be a library you can link directly? Ouch. Add in a Hacker News callback, and this turned into peak open-source drama: half performance tuning, half philosophy fight, with a side of “please don’t make the kernel weirder unless this really matters”.
Key Points
- •The article examines limitations of the traditional Unix/Linux process-creation model based on fork() followed by exec().
- •It states that fork() is costly because it copies process state, including memory, even when exec() may immediately replace that state.
- •Li Chen proposed a Linux kernel feature called spawn templates to optimize repeated launches of the same executable.
- •The proposed API includes spawn_template_create() to build a reusable executable template and spawn_template_spawn() to launch processes with per-invocation arguments and actions.
- •According to the article, the patch set will not be accepted in its current form, but it may inform a future process-creation primitive.