Even already, I think you can get away with doing almost everything v6 with a much smaller number of ipv4s for legacy traffic. I say that but still largely use v4 for everything, so maybe I'm not one to talk.

Unless you need to pull anything from GitHub…

Then direct your anger at Microsoft, not Amazon.

Why not both?

Both are dominating the internet-cyberspace and both screwing it over for everyone else.

Please stick to the topic at hand. Not every mention of a big tech company needs to devolve into a general bitch fest.

There's a collective action problem around IPv4 vs IPv6. Talking about Azure/Microsoft/GitHub and its lack of IPv6 support is very much an interrelated problem. It's ridiculous to think of noting downsides/trade offs as just kvetching.

Why do you need a public IPv4 address to pull from GitHub?

GitHub has no modern IP support, so a system without a legacy IP is unable to pull anything from GitHub.

That's the idea, you route github through a legacy route and use normal route for everything else.

It's ISPs who are the main problem, not applications.

Not software applications, applications of network usage (though I see why it would be reasonable to misunderstand)

Both