That they use IPv6 for their wireless division just makes it more ridiculous that they don't for their wired division - they clearly have the institutional knowledge to make it work.
Except that you probably want a different solution on wired. On mobile just about everybody is running with IPv6-native and the NAT64/DNS64 for IPv4. On wired, you may want to do something different. For example, if some of your customers need a pubic IPv4 address, then you want dual stack. You have to deal with CPEs doing IPv6 correctly, etc.
So it is better to see it as a completely different project. The core routing IPv6 is the same, but that tends to be the easy part.
There are far fewer people who have a contract that specifies that they will get a public IPv4 address on mobile.
On wired, just about every business account is assumed to have a public address and often a static one. In addition, a lot of gaming doesn't work behind carrier grade NAT.
In the mobile world, this expectation of public (or even static) IPv4 addresses is almost completely absent.
And there are over a billion sites. This wall shows the most "popular" sites. I'd like to see the same for the most "popular" ISPs. Getting ISPs to implement IPv6 is important because otherwise is impossible to test your own site and see if it works over ipv6 (i've been there).
Verizon is the big one.
That they use IPv6 for their wireless division just makes it more ridiculous that they don't for their wired division - they clearly have the institutional knowledge to make it work.