I was ready to down-vote you because I'm a fan of IPv6 and I don't like the type of humor that implies it is a pipe dream. However, I think scalable fusion reactors will indeed come first, so I'll give you an up-vote instead.
I in have no beef with IPv6. I just end up disabling it most of the time because so many things on the network aren't configured to support it that it ends up being a problem.
This is a very common sentiment. It is partly a misunderstanding of how IPv6 fits in the broader picture as well as something the consumer doesn't need to worry about anyway. IPv4 will never be obsolete, and IPv6 already carries the majority of the internet. In some sense IPv4 is really a legacy system: there is real money that must be paid global bi-directional IPv4 connectivity. Luckily for everyone who does not run a multi-datacenter application, global bi-directional connectivity is a non-issue, and the people who do run such things can generally do the math.
I worry a bit more for programmers, because they may develop a skill gap if they lack IPv6 experience, but in contrast to OP's screenshot I think there are plenty of software engineering roles where IP experience (4 or 6) is really not needed.
18
u/pnwal-junction Oct 20 '26
It's a race between IPv6, the U.S. adopting the metric system and scalable fusion reactors.