Windows 10 build 17063 and newer (April 2018 Update) supports AF_UNIX sockets, which are statistically faster than using the TCP stack for IPC communication.

Our almost all AF_UNIX usage is for socketpair that Windows 10 does not support yet, so it is still not very useful.

I guess this belongs to the IPC component, but our Windows IPC implementation uses named pipes[1], not TCP. And, to expand on comment #1, our POSIX IPC backend uses both socketpair (to create channels) and SCM_RIGHTS (to send endpoints over channels), neither of which Windows supports yet. In theory named AF_UNIX sockets could be used similarly to named pipes, but that means writing code to do that, and having a dynamic fallback for older Windows, and it's not clear that there would be any benefit. [1] https://searchfox.org/mozilla-central/rev/d4ef4e9747133aa2914aca2a15cf9df1e42a6aa0/ipc/chromium/src/chrome/common/ipc_channel_win.cc