I work for an ISP so I have some perspective on this issue. We do offer static IPv6 addresses to our customers, but only upon request (by default they get one s

I work for an ISP so I have some perspective on this issue. We do offer static IPv6 addresses to our customers, but only upon request (by default they get one static IPv4). If we had demand for it, I'm pretty sure we'd start including an IPv6 subnet by default. It doesn't cost us much, it's just more bookkeeping really. If anything, it could be a turn-off to our customers who might not be used to configuring their router with an IPv6 subnet (the 'ugliness' problem you're talking about, but also just unfamiliarity). I think IPv6 adoption will happen when cloud providers start running out of IPv4 space. If AWS has to drastically raise its prices for IPs, or simply announces they're running out, then AWS customers will have to start evangelizing IPv6 to their own customer bases. Eventually an IT guy in an office says, "I heard Slack is only going to support IPv6 soon, we need it!". So the ISPs start doing it.