I suppose that it would be that easy if we were hosting a website. We make an online game though so the general solution isn't going to work for us.
Sure, in principal it's the same but it's going to require a fair bit more manual implementation in our case, not to mention added latency in a very latency sensitive application.
I think your exaggerating the latency effects but anyway you can still buy IPv4 addresses for ~$12/ip. This is really just going to initially hurt service providers which is good because those are the ones who can make large inroads with IPv6
NATs do induce a fair amount of latency. It's not exaggerated. Watch Paul Saab from Facebook talk about how much better IPv6 performs at NANOG 64: https://www.youtube.com/watch?v=EfjdOc41g0s
They're likely referring to scenarios like this:
https://news.ycombinator.com/item?id=8278864 - "IPv6 privacy addresses crashed the MIT CSAIL network"
& the much more complicated host discovery / address assignment process on IPv6 segments.
Still, I think I'd rather deal with some implementation kinks than intentional packet mangling like NAT.
- own a pseudo-TLD like .com.me and are really just creating subdomains
- have a large account / custom pricing deals with a domain registrar such that despite a high total cost, the marginal per-domain cost is approximately $0
- only internally-routable domains e.g. /etc/hosts or company-internal DNS server
- only alternative DNS roots like Namecoin or tor's .onion domains
