For my home network, I really tried. But in the end, after several times running into weird issues where some pages were working and others weren't, which were reliably resolved by turning off IPv6, I decided to leave the setting in the "Internet works" position.
I don't know what the issue was the last time, and I don't want to know. In particular, I don't want to have to know. When I open the tap, I expect clear, safe, drinking water, not having to debug why the pipe isn't working.
I had these same concerns for a while. Earlier this year, I turned on IPv6 and run a dual stack on my home network (my mac is browsing HN via IPv6.)
Do you remember what sites didn't load for you?
Have you done the tutorial on Tunnel Broker?
No. Because again, I want water to come out of the tap, not spend hours playing plumber.
My ISP provides native IPv6, when it works, and it worked until it didn't, and because I wanted to use the Internet rather than debug the Internet, I took the easy way out. IDGAF whether it was something I could have configured differently that only becomes relevant in some cases, a bug in my router, an issue with my ISPs network, or someone else's misconfiguration: There is a setting in my router, and with the toggle on the left, my Internet works reliably without me having to touch things, with the toggle on the right, it occasionally demands attention at inopportune moments.
I mean in that case yes it makes sense. You are not setting up any networks that affect anyone but you and maybe your family. My comment was directed at people that are setting up infrastructure aimed at hosting systems that consumers intact with or systems that run internal applications, such as an AWS VPC that hosts a variety of services. Your ISP also would fall into that category.