News for hackers. Stuff that matters.
Re:Fork() without exec() is dangerous in large programs (2016) by infogulch on Tuesday June 14, 2022 @04:48PM (#31745861)
The dense fog lifts, tree branches part, a ray of light shines down on the ruins of a moss-covered pedestal revealing the hidden intentions of the ancients. A plaque states "The operational semantics of the most basic primitives of your operating system are optimized to simplify the implementation of command line shells." You look upon the pedestal, pause in respect, then turn away disappointed but unsurprised. As you walk you shake your head trying to evict the after image of a beam of light illuminating a turd.
Re:Fork() without exec() is dangerous in large programs (2016) by tom_ on Tuesday June 14, 2022 @05:06PM (#31746100)
They called it RISC iX because it was RISC.

They called it Minix because it was mini.

And they called it POSIX because...

Re:Fork() without exec() is dangerous in large programs (2016) by junon on Tuesday June 14, 2022 @09:11PM (#31748012)
I've literally never heard this one before. Good one!
Re:Fork() without exec() is dangerous in large programs (2016) by infogulch on Tuesday June 14, 2022 @04:50PM (#31745882)
I wrote this silly little bit on a previous fork() thread and touched it up a little. https://news.ycombinator.com/item?id=30504470
Re:Fork() without exec() is dangerous in large programs (2016) by cryptonector on Tuesday June 14, 2022 @05:29PM (#31746319)
It was a glorious comment then, and it is now.

BTW, it's unclear whether the turd is... the specific truth revealed, or the revelation itself (since it could be incorrect). It's still a glorious comment.

Re:Fork() without exec() is dangerous in large programs (2016) by infogulch on Tuesday June 14, 2022 @06:19PM (#31746740)
Thank you! The goal was to evoke the same emotional response I felt when this idea struck me (I think when I was reading earlier comments in that thread in fact), so I guess there's as much in the sequence as the specific objects. The semantic design of fork was always incomprehensible to me (not what but why), so the setting and pedestal and plaque represent how strongly it struck me and the depth of its historical explanatory power. The turd is how I feel about it. I don't resent the designer's history or motivations or incentives and I'm happy to know the truth. I'm just sad/depressed that this is the reason why things are the way they are, that the original design intent is so misaligned with the needs of modern systems, how it limits our capabilities today even down to hardware, and how unlikely it is for this to change. I don't suppose a turd would last very long on a pedestal, or that the ancients would put a turd there on purpose. Maybe they put something beautiful there back then, but times have changed and now we're stuck with it and it's kind of shit.
Re:Fork() without exec() is dangerous in large programs (2016) by cryptonector on Tuesday June 14, 2022 @06:23PM (#31746776)
Don't get too sad about legacy. A lot of things were brilliant once that aren't now. I do still feel that fork+exec was brilliant then, just not now. Deprecation is hard, but we can celebrate what legacy made possible.

Now, if only we had a time machine...

Re:Fork() without exec() is dangerous in large programs (2016) by infogulch on Tuesday June 14, 2022 @06:53PM (#31747006)
Agreed. I'm not sure where to go from here, but I think I smell fresh air through the WASM/WASI doorway.

"If in doubt, Meriadoc, always follow your nose." - Gandalf

Re:Fork() without exec() is dangerous in large programs (2016) by cryptonector on Tuesday June 14, 2022 @07:10PM (#31747136)
WASM, making lemonade out of lemons (JS).