Re: Using IPv6
Do you honestly think that even 1% of 1% of people even handle an IP address or know what it is?
Hex is simpler to check, to type, to copy, to handle than binary - nobody deals in binary for IPv4 anyway! I'm a mathematician and the times I actually need to subnet, I just use an online tool - even though I'm perfectly capable of masking the binary myself, nobody WANTS to use binary anyway.
IPv6 is there, it works, it's in every major OS, it's REQUIRED in DOCSIS (cable Internet, since 2006! 13 YEARS!) and 3G/4G services (even if it's not used, but your phone probably already uses it and you don't even know). There is no excuse, but certainly "hex vs binary" doesn't even come close to consideration.
Any IT guy managing any significant number of networks or computers barely touches a binary number in his life, and probably deploys entire networks with only two or three locations even containing or requiring an IP address (DHCP ranges, Gateway machine, DNS servers). I honestly don't know, care or need to know the IP of any of the hundreds of machines, dozens of servers (virtual or otherwise), VPNs, outside servers or anything else that I manage. I copy paste the output from my DNS server when I need to (e.g. I nslookup server.domain.com, copy the IP and paste that into the VPN or whatever - and that's assuming it's so dumb that it can't resolve that itself!)
And... internally... it doesn't matter WHAT I use. All I need is a gateway that does 4->6 translation, that's it. Done. Online, forever, via IPv6, who cares what my internal numbering is? One device, one IP address range, plugged in once, when I set up an Internet connection / router. Most people *never* have to do even that. They get a router in the post, plug it in, join the specified wifi, and they are up and running. There is literally no change required to that process to allow every home user to use IPv6... all that changes is the *external* address, you're all still using 192.168.x.x internally anyway!
The poor arguments trotted out against IPv6 are honestly pathetic. Turn it on. Add an AAAA record (if you can manage DNS, you can copy/paste an IPv6 address from the output of ip addr/ipconfig). Ensure the final connection upstream has an IPv6 address and appropriate network translation (which you're GUARANTEED doing anyway, because you'll be using the reserved ranges inside the network), done. And that's for the frontline, techy staff running huge businesses, offices, etc.
ISPs are the hindrance. They just don't want to turn it on. Datacentres have been onboard for years. Outside websites are a cinch (my own personal website is 6 already, as well as the time-server I provide, VPN I use, my dynamic DNS account, etc. etc. ) ISPs are the one category of business that needs to hire people who understand IP addresses (and "binary" as you put it). That's it. If your existing guys implementing your ISP on a national basis don't understand IPv6, just sack them now, immediately, totally, no-questions.
The reason is - it's a business expense to change it, and they won't do it while they're hoarding IPv4 addresses because... shock, horror... they could always make the whole thing work for everyone by deploying IPv6 at their boundary and carrier-grade NAT could do 4->6 as well.
Stop the pathetic excuses. Enable services. Turn the little switch on in Windows. Done. The only thing stopping people like me (who have IPv6-capable internal networks, IPv6-capable services all over the place, and barely a line anywhere that even mentions IPv6 except by default (e.g. Apache binds to all the local network addresses itself already anyway!)) is that my ISP do not provide me with an IPv6 address. They carry the packets, they do everything else. They just don't offer an IPv6 allocation.
But they're already doing it for every mobile phone carrier, their back-end networks for cable customers, even their VDSL networks, etc. They just won't run the IPv6 equivalent of a DHCP server for their customers. Hell, most of them run the 4->6 addresses!
It's been out for 20 years, working fine for over 10, been in every major OS in that time. That's more than enough time to "learn binary", especially given that you only need one guy per ISP who actually understand "binary" to start implementing it.