Chrome 69: “www.” subdomain missing from URL
<i>&gt; This is a dumb change. No part of a domain should be considered &quot;trivial&quot;. As an ISP, we often have to go to great lengths to teach users that &quot;www.domain.com&quot; and &quot;domain.com&quot; are two different domains...</i><p>What ISPs teach their users anymore these days? Why the heck do we want to go back to that?<p>Time for a modicum of historical perspective.<p>If you care about usability this is clearly an improvement. This is part of a long-running industry trend -- Safari does this too -- to improve the usability of the Internet and technology in general.<p>At EVERY STEP in that journey there has whining and griping from the more technically advanced folks (like all of us on this forum). They zero in on the negatives, the tradeoffs that come with simplification. They don&#x27;t see the positives because they&#x27;re technically advanced enough and don&#x27;t benefit from simplification (or so they think).<p>Then after the griping whines (sic) down and they realize the world didn&#x27;t end and the downsides really weren&#x27;t that bad and we move forward towards a better, simpler, more usable web.<p>Like, who actually runs separate HTTP servers on example.com and www.example.com anyway? Everyone is hyperventilating over contrived &quot;the principle of it all&quot; examples. Bottom line, Apple &amp; Google are putting usability above technical pedantry. That&#x27;s the right priority for mass market technology products.