Yeah I don't get it. If you need to access IPv4 for legacy reasons then dual stack seems like the solution here. Yes it's a lot of overhead since you have to deal with an IPv4 and IPv6 routing table. AFAIK Windows has had both enabled by default for a long time.
This is actually a very good workaround/transition mechanism, because it lets you go fully IPv6 native, keeping the translation layer for things that absolutely must use IPv4.
And after transition is done, in theory, all you’d do would be turn off the translation box. In practice you’ll have to keep it up until the end of days, but that’s a separate matter.
An average user is not expected to do that. But I understand there are mobile operators out there who have been doing this (instead of NAT) for a while because they don't have IPv4 addresses for every consumer subscription? Wasn't T-Mobile US one of them? (Not living in the US.)
An average user shouldn't be able to find hardware not supporting IPv6, because it shouldn't be allowed to be sold. (And soon, hardware supporting IPv4.) Just like it happened with digital TV standards.
In home network single $70 USD device with 2 daemons running may be clearly too much but for corporate or even office network it's just one more box in addition to dozens of network devices.
