so when i dislike changes in software i’m “weird” and i should “get on with the times”, but when you don’t wanna do IPv6 because it’s new and scary (TO YOU) it’s suddenly okay?
come on…
so when i dislike changes in software i’m “weird” and i should “get on with the times”, but when you don’t wanna do IPv6 because it’s new and scary (TO YOU) it’s suddenly okay?
come on…
ipv6 isn’t without flaws. but have you SEEN the general software landscape? the things that we put up with on a daily basis?
if we waited with software to be “perfect” as much as we seemingly do with networks, computers would still only be strictly experimental mainframes
@emilia i’ve heard this exact story echoed from others a bunch of times, but. it’s even worse when you’re self-taught.
i’m being told that my style of technical writing is really easy to understand, so I feel like I may be a good pick to work on something better…
@domi
> insufficient education
*looks at purely static ip assignment, overuse of ULA and complete cluelessness on NAT64 at work* yeah…
@domi It's *checks watch* 2026 and my ISP doesn't support IPv6 to residents, like not even a /64 (a reminder that a /48 is appropriate for a residence, I would get a /32 if I had a big network).
They assigned /127s last time I turned off bridge mode.
@domi Big education problem. Especially with infrastructure that isn't the "cool" thing anymore. Everyone wants to do shiny software these days.
Sadly, a lot of teachers didn't touch operational stuff in the last decade and won't in the next and those are the ones that are training the techies that will touch the infrastructure for the next 20 years... Had to go through that