I do! But then I ask those people to explain how to go about doing v6 in a way that isn't rubbish, and the only answers I get to that are a) impossible, b) no answer/refuse to answer, or c) they start reinventing v6 but with weird names for everything. Or some combination of the above ("just add two octets and have a flag day" is a common one, combining (c) with (a)).
I've more or less come to the conclusion that the people who think v6 is bad don't know what they're talking about. If none of these people can come up with a better approach than v6, that suggests that v6 really is more or less the best approach available.
> after almost 3 decades and so much the adoption at 50%
I think we all wish it had been faster, but the v4->v6 transition is the first time humanity has ever done a transition like this, on this scale, involving so many disparate networks controlled by so many people in so many countries. How do you know that 50% at 3 decades is slow? Maybe this is just the par time for this kind of thing.
The answer is something like:
https://www.ietf.org/archive/id/draft-thain-ipv8-00.html#sec...
They key things is that pretending interoperability with IPv4 can be an after thought or dual stack is a good idea was just stupid and proven to be so. Flag day or IPv4 fading into oblivion never going to happen.
I know 50% is slow because that is LESS than new deployments over the past 3 days, so if someone thing “better” can be deployed to new projects until all old projects migrate is broken.