> Surely you are aware there is zero standard for the functionality you're referring to. Aside from being patently false—shared memory is standardized by IEEE

> Surely you are aware there is zero standard for the functionality you're referring to. Aside from being patently false—shared memory is standardized by IEEE 1003.1 POSIX[1][2][3] and supported on all modern unices—that's a pretty disingenuous and bad-faith assertion. But anyway: 1. 'shmem' refers generally to the ability of memory pages to mapped into multiple processes' address spaces. The existence (or lack thereof) of any particular implementation does not invalidate the broad point, which refers to a capability which tends to be implemented in some way on arbitrary platforms. Of course, if you want to develop a particular application which uses shared memory, you will want to make decisions about which platforms you want to support and how you want to support them. Of course, this may involve using platform abstraction layer (like openmpi), or building your own, or intentionally tying yourself to a platform or group of platforms. None of that has any bearing on my point, but it does lead to: 2. The functionality referred to in the linked video—that of composing multiple disparate applications with pipes—is one that is uniquely associated with unix. Thus, it is reasonable to assume that any critique of said functionality operates within the framework of unix. And all unices newer than 30 years implement sysv shmem[4]. 1. https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/sys_shm.h.html https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/sy... 2. https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/sys_mman.h.html https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/sy... 3. https://pubs.opengroup.org/onlinepubs/9699919799/help/codes.html#SHM https://pubs.opengroup.org/onlinepubs/9699919799/help/codes.... 4. https://tldp.org/LDP/lpg/node21.html https://tldp.org/LDP/lpg/node21.html