Interesting! The Wikipedia article is quite wrong here. SOCK_STREAM certainly doesn’t imply TCP in all cases. I see the source is the Linux Programming Interface book; quite likely someone’s interpretation of that chapter was just wrong when they wrote this article. It is a subtle topic.
Hey! I know it’s muddled but that’s not quite correct. SOCK_STREAM is more general than TCP; SOCK_STREAM just means the socket is a byte stream. You would need to add IPPROTO_TCP on top of that to pull in the TCP stack.
UDS using SOCK_STREAM does not do that; ie, it is not using IPPROTO_TCP.
Yep! I should mention that on the website. The only thing that was innovative about that is doing docker-in-docker builds which is as simple as mounting /var/run/docker.sock:/var/run/docker.sock in the container. Zero downtime deploys make it sensible for it to deploy itself, and then restart. And it really breaks, I still know how to deploy from my laptop to get myself out of a pickle.
Sure, take a worse-case interpretation of my words, this is the Internet after all.
We're all posting short messages here, not essays.. There is so much room for choosing to interpret each other in different ways.. So it's inevitable that we'll be misinterpreted sometimes.
And yes, I did try to reframe to better make my point, because I do think I'm right.
Welcome to HN, but a word of advice, this kind of snipey low-value shitpost is typically not welcome here.
