3 ms·

I think two reasons: 1) VxWorks directly supports message passing (http://www.vxdev.com/docs/vx55man/vxworks/ref/msgQLib.html http://www.vxdev.com/docs/vx55man/

I think two reasons: 1) VxWorks directly supports message passing (http://www.vxdev.com/docs/vx55man/vxworks/ref/msgQLib.html http://www.vxdev.com/docs/vx55man/vxworks/ref/msgQLib.html). 2) They seem to prefer simple, obvious, "less magic" interfaces. STM is nice for its "magic", but message creates very well defined, documented interfaces between code.

deno 14y ago
> STM is nice for its "magic", but message creates very well defined, documented interfaces between code. The author’s previous post has a good overview of how message passing contributes to that as well. http://jlouisramblings.blogspot.com/2012/06/protocols-in-kingdom-of-distribution.html http://jlouisramblings.blogspot.com/2012/06/protocols-in-kin...