3 ms·

Thanks to Julie for this; but I'm still a bit confused. Does anyone share a suspicion that these myriad of anachronisms and bits of weirdness creates unnecessa

Thanks to Julie for this; but I'm still a bit confused. Does anyone share a suspicion that these myriad of anachronisms and bits of weirdness creates unnecessary complexity that swim through the system like a goblin in the machine? And that, if with 20/20 hindsight we just simplified things a bit, that many of our systems would be much more resilient and easy to manage? I feel that we hacked the internet together, and in the impending rush to build more and more on top of it, we just resigned ourselves to the mess. None of this (well, most of it) should be inherently hard. If we 'did it with foreknowledge' I wonder if all of these IT level networking issues would be pedantic, i.e. something you read a few quick docs and away you go. Everyone an expert pretty quick. Merely looking at the options for my DSL device, my god man, even after all these years in tech, I'm still a bit bewildered. Even at the consumer level, if I go over to someone else's house, I can't 'change the channel'. No idea what I'm watching, or the abstractions behind how it got to the TV.

xani_ 4y ago
A lot of them, absolutely, but this particular one had for a long time (arguably still has) useful properties. Like if you're inside same network you can just connect to "db" server and don't care what's the rest of the FQDN is. Similarly with typing "ssh app1" vs "ssh app1.example.com" Starts to matter where your k8s address can be <service>.<namespace>.svc.kube.example.com > Merely looking at the options for my DSL device, my god man, even after all these years in tech, I'm still a bit bewildered. A lot of DSL dumbfuckery came from telco. For example, ADSL uses ATM framing which is 64 bytes, with 48 bytes of payload. And it is fixed size packet which means mere TCP ACK, with all header overheads, won't fit and you need to send at least 2 ATM packets for each TCP ACK AND waste some bytes in them too. ATM was first used for voice which is where constant size came from. The VPI/VCI settings are also directly related to ATM protocol And why 48/64 byte ? Coz EU wanted 32 byte payload (coz they wanted lower delays) , US wanted 64 byte (coz they wanted lower overhead) and they just split the difference in the middle. Why the fuck they applied it to inherently point to point ADSL ? Who the fuck knows, you'd think throwing away 25% bandwidth on ATM header would be bad for residential service over shitty wires but they apparently didn't care.

xani_ 4y ago

A lot of them, absolutely, but this particular one had for a long time (arguably still has) useful properties. Like if you're inside same network you can just connect to "db" server and don't care what's the rest of the FQDN is. Similarly with typing "ssh app1" vs "ssh app1.example.com" Starts to matter where your k8s address can be <service>.<namespace>.svc.kube.example.com > Merely looking at the options for my DSL device, my god man, even after all these years in tech, I'm still a bit bewildered. A lot of DSL dumbfuckery came from telco. For example, ADSL uses ATM framing which is 64 bytes, with 48 bytes of payload. And it is fixed size packet which means mere TCP ACK, with all header overheads, won't fit and you need to send at least 2 ATM packets for each TCP ACK AND waste some bytes in them too. ATM was first used for voice which is where constant size came from. The VPI/VCI settings are also directly related to ATM protocol And why 48/64 byte ? Coz EU wanted 32 byte payload (coz they wanted lower delays) , US wanted 64 byte (coz they wanted lower overhead) and they just split the difference in the middle. Why the fuck they applied it to inherently point to point ADSL ? Who the fuck knows, you'd think throwing away 25% bandwidth on ATM header would be bad for residential service over shitty wires but they apparently didn't care.