Exactly, thank you! I think first and foremost the browser should be clear and easy to use for the general user, not an easy to debug frontend for devs, if we do that the browser will be a mess. Devs know where to look to see what the real address is if they get reports of there site not working, and can then fix the issue on their end. It's not like the issue isn't something that you can't change on the server end.

The people who run the sites should do all they can to make the experience as hassle-free as possible. This means no www.domain.com and domain.com going to different places, 99% of users will expect to end up on the same site regardless of where you add the www or not, to them it's the same as adding the htttps or not, it should "just work" regardless what they put in the front on the URL. (of course there will always be some edges cases, but I feel it's worth it for a better end-user experience.

IDK, just my 2c.

Not sure why you are getting downvotes but I agree with you here. I think this change is going to benefit both technical and non technical users. How many websites make the mistake of not handling www and non-www the same? Or having a valid certificate for both domains? It's not just a pain for the non techies