This program isn't meant to be multithreaded, it's meant to be multi-/process/. The difference is that each instance of the application has its own independent address space. So that's one address space per instance. And because of that there are no threading issues. Also as a result any communication between different processes has to be explicitly defined.
Making this program multi-threaded would be a big mistake because then you couldn't use any of the HTTP proxies out there to monitor for connections and hand them off to this program.
This is arguably a much better architecture from a safety/security standpoint then trying to spin multiple threads each sharing an address space. It forces you to use OS-provided mechanisms for shared state rather than simply manipulating the memory to share information.
It’s rare with LSD but occasionally they’ll substitute a research chemical with similar effects. You’re more likely to have that happen with “MDMA” that is actually methamphetamine or one of the analogues. Both are horrible.
There are places that sell home testing kits which are very useful since you don’t know what you’re getting by looking at it. People used to test for each other at raves until the police said it was a form of condoning drug use and shut it down. So now people still buy but it’s more dangerous.
I expect my reports to tell me if I'm being unreasonable. But then I've worked to build trust with them such that they know I'm not going to fly off the handle if I give them a directive and they push back. In fact I tell them. "Hey, if something I'm saying seems crazy to you please tell me. I know what the project needs but I don't always know what you know about what I'm asking you to do."
If someone blows up at me for being direct, I'm going to PIP them and move them off my team and out the door.
Wouldn't there be idioms in the assembly which represent compatibility with the old ABI? Couldn't you translate those directly in the assembly without having to re-run the compilation?
ABI describes things like how the stack works, but at the assembly level the only stack is the one you implement, which is generally compatible with an ABI version.
This program isn't meant to be multithreaded, it's meant to be multi-/process/. The difference is that each instance of the application has its own independent address space. So that's one address space per instance. And because of that there are no threading issues. Also as a result any communication between different processes has to be explicitly defined.
Making this program multi-threaded would be a big mistake because then you couldn't use any of the HTTP proxies out there to monitor for connections and hand them off to this program.
This is arguably a much better architecture from a safety/security standpoint then trying to spin multiple threads each sharing an address space. It forces you to use OS-provided mechanisms for shared state rather than simply manipulating the memory to share information.