We aren't. There's a variety of reasons people choose to use v4 (some good, some bad), but you don't have to.

The network my desktop is on doesn't use v4. It works. v4 isn't a required dependency.

Indeed. And many mobile networks are also v6 only with a translator like xlat at the edge for compatibility with anything still on v4 only. And since so many people get internet only from mobile this is becoming a norm.

How do you get to github? How do you connect to hackertimes.com? Why is an IP address more valuable than an IPv6 address? Why is IPv4 the incumbent 30 years after IPv6?

> How do you get to github?

  $ wget https://github.com/
  Resolving github.com (github.com)... 64:ff9b::8c52:7204, 140.82.114.4
  Connecting to github.com (github.com)|64:ff9b::8c52:7204|:443... connected.
  HTTP request sent, awaiting response... 200 OK

> How do you connect to hackertimes.com?

  $ wgetnull 'https://hackertimes.com/
  Resolving hackertimes.com (hackertimes.com)... 2606:7100:1:67::26, 209.216.230.207
  Connecting to hackertimes.com (hackertimes.com)|2606:7100:1:67::26|:443... connected.
  HTTP request sent, awaiting response... 200 OK

> Why is an IP address more valuable than an IPv6 address?

Because there's such an incredible amount of v6 addresses. You could pay a trillion dollars per second for a /64 and still only pay $1.70/year for each address.

> Why is IPv4 the incumbent 30 years after IPv6?

Because IPv4 was the only choice until IPv6, and replacing the Internet's L3 protocol is hard and takes a long time.

> How do you connect to hackertimes.com?

PSA that hackertimes.com is 2606:7100:1:67::26 now.

That is all. Except for the part where it doesn't help us on IPv6-Never ISPs.