It depends on how you measure IPv6 adoption. Is it about your ability as consumer to use only IPv6, or your ability to offer a website reachable only via IPv6.
AWS charging for IPv4 will help with the former, because companies now have more of a reason to care about IPv6. But it might delay the latter, because fewer IPs wasted on internal servers means less price pressure on useful IPv4 use by ISPs, giving those that still hold out less financial incentive to change anything.
IMHO, best way to measure IPv6 adoption would be - what percentage of your website's visitors are able to reach your IPv6-only site.
That percentage should be well above 99% for a popular website operator to even consider going IPv6-only; needless to say, in most markets, this figure is way lower, with no clear path to improving.
It doesn’t help that, if you enable IPv6 in Debian, the network becomes extremely slow for many things. The reason? If first tries to reach all domains with IPv6, times out, then use IPv4. Of course that’s because I didn’t successfully configure IPv6 with the network, but on the other hand, IPv4 only was successful at first try.
That's not how v6 works in Debian, or really anywhere. For one thing, you can't reach a domain with v6 if there's no AAAA record, so it certainly won't be trying to reach "all domains" with v6.
If your network has broken v6 then yeah, that's gonna cause problems. That's not v6's fault, that's down to having a broken network.
Linux doesn't have a big "enable IPv6" switch, so it's not clear what you mean.
The only way I can think of getting the behaviour you describe is if you configure the network to hand out v6 addresses and routes to hosts, and then just black hole the packets. What you have then is a broken network.
But this is also AWS exerting price pressure on its customers. This move is an increase in price pressure, not a decrease.
If everything host on AWS becomes dual stack and gets first class IPv6 support after this move, that's a win for IPv6.
The price for v4 address is going to bob up and down as more networks and content providers adopt v6 and are able to reduce their public v4 usage to just their edges.
There will definitely be a long tail of v4, especially in the corporate world, but I think we'll get to 90-95% v6 capable within the next 5-10 year
AWS charging for IPv4 will help with the former, because companies now have more of a reason to care about IPv6. But it might delay the latter, because fewer IPs wasted on internal servers means less price pressure on useful IPv4 use by ISPs, giving those that still hold out less financial incentive to change anything.