วีดีโอ

damnn.... i didnt understand anything

Last sentence hits hard

Literally the reason react is still alive

lmao

In the next episode: React is dead and his body is taken over by Next.js

Learned something but I don't know will I ever use it or not. lol Just use multiple session in tmux

Just open 2 terminals LOL 😂

Super neat stuff!

very good content, thanks

What if I provision a TLS through PKI or a local root CA ? Then can the traffic be routed through port 443 ?

Socket files can run entirely in memory! Crazy `> find / -type s ` is super helpful

Is it used in real life? PHP-FPM makes heavy use of Unix Domain Sockets. Most databases use them as well. If you’re running a website on a single system I am pretty sure Unix Domain Sockets are involved somewhere.

Great video! Btw what do you use for the slides?

Every time I see this thumbnail I click into this video. It is on par with the quality of the contents

I was liking this video until you said the example in JS...

why i just found you!!!!! THIS VIDEO IS GREAT TRICK FOR CORPO LIKE GITHUB HAHA

Linus Torvalds domain expansion is Linux.

I'm in tears

gud

MySQL also use Domain sockets

insane thumbnain lmaoi

nice vid. Subbed

Yes, it supported under Windows, but only as a wrapper around named pipes. For most software this slight overhead is unnoticeable, but if you need to squeeze every last drop of performance, you'd might want to use named pipes directly. But than again, if this communication is the bottleneck of your application, you already have most likely already made some bad design decisions earlier. Usually IPC is used to communicate from a user-space front-end utility to a background service/daemon process, but in some cases it also used for communication between forked processes...

In Windows, it's not available to non-insiders.

Why the GenZ call-out?

1:36 One Piece ftw

Under rated content

Not the domain expansion 😭 it's perfect

nodejs jaw line is insane

Which theme are you using?

Why da fock are you writing socket shit in js

Anyone have a comparison of the throughput difference between domain and TCP sockets, when both processes are running on the same machine?

This is both idiotic and genius.

It’s that easy to use Unix pipes?? And here I am using a whole-ass server like a sucker.

I wonder which other programs you might want to add to that development environment

Wow Sun Tzu really was ahead of his time :P

I have a project on github that uses socket servers. Made it years ago

make a discord so i can annoy you when im bored

can u please show? how u make those video?

10/10 thumbnail

I keep watching this even though I’ve already known what a UDS is. For the thumbnail.

I think it's valuable going over the rest of the list and some further reasons why you would want this over another. It seems half done, really.

Bruh I've been searching for this for a week now

"No bloat" Proceeds to use nodejs

What do you use for terminal ascii art?

why is it just plain black?

I don’t know enough about Node.js to say this for sure, but at least in C TCP sockets, you have to also deal with the fact that sometimes messages are encoded across multiple chunks, meaning you have to build you own buffers and the like. HTTP libraries generally abstract this for you. If you want something you described, I think that ZeroMQ is a much better system. That still has almost no overhead over raw TCP sockets, but handles that chunking and the like for you.

Nice content, keep bringing it, please!

Linus Domain expansion : sudo rm -Rf. Not even Sukuna can counter this.🤣

The domain expansion thumbnail is the only reason I clicked on this. And I'm glad I did.