Programmer Humor

19557 readers

1029 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

Keep content in english
No advertisements
Posts must be related to programming or programmer topics

founded 1 year ago

MODERATORS

[email protected]

357

Basically the extent of my IPv6 knowledge (lemmy.world)

submitted 4 months ago by [email protected] to c/[email protected]

28 comments fedilink hide all child comments

Template source: https://web.archive.org/web/20210304000634/https://www.government.nl/topics/coronavirus-covid-19/visiting-the-netherlands-from-abroad/checklist

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 46 points 4 months ago (13 children)

Should probably fix that given we've been out of IPv4 for over a decade now and v6 is only becoming more widely deployed

[–] [email protected] 28 points 4 months ago (6 children)

Agreed. Though I wonder if ipv6 will ever displace ipv4 in things like virtual networks (docker, vpn, etc.) where there's no need for a bigger address space

[–] [email protected] 5 points 4 months ago (2 children)

I wish everything would just default to a unix socket in /run, with only nginx managing http and stream reverse sockets.

[–] [email protected] 4 points 4 months ago (1 children)

Wait, but if you have, for example an HTTP API and you listen on a unix socket in for incoming requests, this is quite a lot of overhead in parsing HTTP headers. It is not much, but also cannot be the recommended solution on how to do network applications.

[–] [email protected] 1 points 4 months ago

Replacing a TCP socket with a UNIX socket doesn't affect the amount of headers you have to parse.

load more comments (3 replies)

load more comments (9 replies)