Meanwhile in both India[1] and China[2] (two biggest countries by Internet users count) IPv6 is mandated by the national policy. Everyone else should do that, otherwise the transition would never be finished. ISPs and other network businesses should be forced to do upgrades by the law or policy, otherwise they will never allocate budget and resources for that.
I have had a dual stack at home and work for around a decade now but "Everyone else should do that" is a bit proscriptive.
If it ain't broke (and it really isn't quite yet) then I suggest we crack on. IPv4/6 are simply transports, one has a larger address space and quite a lot of attitude! There are translation mechanisms so it is unlikely that anyone will be left behind. As systems move to IPv6, parts of IPv4 space are released and 6to4 n that tunnels can patch up the holes.
You need to learn patience. It took me about two years to persuade a firm with around 6000 employees to deploy DHCP back in the day. I made sure it was everyone else's idea and took my time. That was a tiny thing. This is the entire internet and it requires a massive mindset shift, engineering, purchasing and what not.
I'm going to tentatively put IPv4 -> IPv6 in the "paradigm shift" category. It isn't really technically: the wires (ethernet etc) are the same but the bits are somewhat different!
If you really want to get steamed up then why not debate the semantics of how multi-WAN connections should work with IPv6? Suppose you have two ISP connections for WAN and hence two lots of addresses. How do you deal with an ISP outage? How do your PCs know which set of source addresses to use? Do you use NAT64 or NPT or something else.
Another thing to consider is how do you "bootstrap" your network with IPv6 and how do you deal with a change of ISP? Do you set DNS servers with ULA addresses so they stay static or what? Bear in mind that SLAAC doesn't give out DNS servers. OK, lets do DHCPv6 ... not on Android ...
IPv6 needs some care. It has been messed and muddled around with so many times and it still has some gaping holes. For me the biggest problem is the righteous indignation you find at nearly every turn where stuff gets broken for its own good.
It all starts to go wrong with "everyone should"!
The starry eyed approach that you think that India and China espouse is simply twaddle. No one really thinks that in the real world, despite what is said on TV. Nation policy of that sort is normally a case of "Do as I say and not as I do".
In my opinion we should damn well continue to muddle along as best we can with what we've got. We will patch the flaws and paper over the cracks because that is what engineers do.
Another elephant in the room: /64, /56, or /48. The first one is completely unacceptable in the modern world, the second is acceptable and the third is desirable ... per ISP connection.
If you only get a /64 ie one IPv6 subnet prefix then you are only a tick in a box.
Ideally you also get a separate uplink subnet too along with your shiney prefix for WAN. There is a RFC that will enable a sub-prefix from a prefix allocation to be taken out for WAN and make it all work. Sorry if that sounds like gibberish - I won't explain that lot here!
There are so many things to get sorted with IPv6 - it is not a finished thing. It's only about 40 or so years old.
[1] https://www.indiatimes.com/technology/news/india-sets-new-de...
[2] http://www.stdaily.com/English/ChinaNews/202208/e154b19bb5b0...