> They couldn't have made the client stub interface more baroque if they tried. I've never used this API but the cross process synchronization stuff seems like

> They couldn't have made the client stub interface more baroque if they tried. I've never used this API but the cross process synchronization stuff seems like a difficult nut to crack. I'm curious which bits you think are unnecessarily baroque. > If you can stomach the perf tradeoffs, compiling to WASM is much easier than this I'm not super familiar with WASM, but it's unclear to me how compiling to that target addresses the problems that are addressed by this system? Does WASM have built-in security policies and sandboxing? Is it easy to call into a WASM-compiled library from your native C/C++ program? How?