Relatively rarely, but in some performance sensitive use cases. Mine happens to be fuzzers, where a very cheap fork-like primitive would be a really big win.
There are a lot of slightly different fork-exec-like things in the concept space and it's hard to imagine one approach satisfying them all. IMO it would be interesting to take an approach analogous-ish to sched_ext_ops where you built the rough flow chart of a combined fork-exec, but with hooks built to enable ebpf to change behavior or skip the bits these sophisticated users don't want/need.
You can do this with some forms of trip insurance. I stared hard at arbitrage there a few years ago but it was too hard to get your money out if you were right.
I'm encouraging my folks to try it pretty hard because A) I've personally seen the productivity gains and B) using it is at first deeply weird/uncomfortable. Sometimes you've got to convince people to push through that kind of thing.
I hear about meow wolf all the time and I seem to be the only person in the world who thought it was an underwhelming cash grab that is beaten by a half dozen events a year in nearly every major city in the US. Am I just missing some huge piece of it?
Not meaning to derail an interesting conversation, but I'm curious about your description of your work as "applied probability". Can you say any more about what that involves?
It isn't impossible that it's AI, but assuming writing and publishing happen at the same time would also lead you to conclude that Anne Frank wrote from the afterlife.
Every time I see one of these stories I wonder how many tools I would have to remove from my garage to make it impossible to build a primitive gun in there. With enough ingenuity I'm really not sure there would be anything left.