4 ms·
It’s really too bad that ipv6 is only… checks notes… 26 years old now. I realize that may be an unreliable metric, so it’s roughly equivalent to 2.88 react.js l
by ipython 4y ago
It’s really too bad that ipv6 is only… checks notes… 26 years old now. I realize that may be an unreliable metric, so it’s roughly equivalent to 2.88 react.js lifetimes, or 3.25 vue.js lifetimes.
When the ipv6 spec was released, the latest python release did not yet support list comprehensions.
In other words, there is no reason to not support ipv6 out of the box in 2022.
- oxplot 4y ago> there is no reason to not support ipv6 out of the box in 2022 Use the age of a service as the metric, not the absolute year we're in. It's probably reasonable to say that there is little reason not to support IPv6 for an ISP with X years of operation. Starlink is young still. An analogy is worldwide sales for a new laptop company. You can say that in the age of globalism, there is no reason not to ship to every continent right off the bat. But for a startup with limited cash that has lot of building blocks to lay out, it's a huge risk. They should plan for it, but only branch out when they've got a solid foundation.
- wmf 4y agoA new ISP should implement IPv6 first and then run IPv4 on top of it like T-Mobile. They shouldn't "add" IPv6 because it should have been designed in from the beginning.
- p1mrx 4y agoA better analogy would be a new laptop company selling laptops with Windows XP. "Our staff is more familiar with XP. We promise we're still working on the Windows 10 drivers, but in the meantime you can try to run it in VMWare."
- znpy 4y ago> In other words, there is no reason to not support ipv6 out of the box in 2022. i'd go even further and say that no ipv6 support means obsolescence.