5 ms·
You're missing jwr's point. He's arguing that this is harmful for users, especially the ones who don't know what the words mean. If I were solving this, I'd in
by wpietri 8y ago
You're missing jwr's point. He's arguing that this is harmful for users, especially the ones who don't know what the words mean.
If I were solving this, I'd instead push to eliminate "www" altogether, not sweep it under the rug. It was useful circa 1996, when users might plausibly be using something other than the WWW with a browser. But it has become entirely vestigial.
- tribune 8y agoHow can you eliminate "www" altogether? It's just a subdomain like any other now
- stedaniels 8y agoIt's actually very useful for isolating access to the root of the domain. Say for instance you use a third-party SaaS/CMS to host your website and have other services on other subdomains. If it's hosted on the root of the domain it had more power than if it's on a subdomain.
- uberman 8y agoWhy not drop .com then as well? Most sites are on .com domains after all. It is exactly the same issue. A domain is a domain. Google is arbitrarily dictating your CNAME from the user's perspective. What if you don't serve your site off of mysite.com is google going to automatically try again at www.mysite.com? What if you have distinct content at both domains? This decision is stupid.
- deleted 8y ago[deleted]
- wpietri 8y agoIt's not the same issue at all, in that domains with different suffixes are controlled by different people while foo.com and www.foo.com are controlled by the same people. If you have an example of somebody who needs to serve different web content for foo.com and www.foo.com, I look forward to seeing it. But I've never seen one, and when I've seen it happen accidentally it's due to idiocy.
- subway 8y ago> while foo.com and www.foo.com are controlled by the same people Sometimes. Far from always. In some environments, `www` may be under an entirely different administrative domain, with lesser authority than the top level domain which is delegating web services to the `www` group by way of creating a dns record and/or adding an http(s) redirect to the parent domain. Having some string values arbitrarily considered trivial is dangerous. See: lbl.gov has address 128.3.41.146 vs www.lbl.gov has address 35.196.135.136 The root domain points to hosts at the lab. The subdomain has been delegated off to Google.
- slg 8y agoIsn't that simply due to internal politics? Whoever owns foo.com might delegate www.foo.com to someone else, but they ultimately control both.
- ryandrake 8y agoEither way, www.example.com and example.com can differ in terms of IP address, underlying hardware, actual website content, and probably other things I don’t know. They are different URLs. It seems problematic to assume they are the same.
- wpietri 8y agoNot at all. People already assume they are the same. And they have for 20 years. Nobody reasonable serves up different content on the two URLs. Anybody clueful redirects one to the other. The only reason they're separate is that a) the web wasn't dominant when it was introduced, and b) technology of the time made it hard to manage traffic in ways we can now.
- ryandrake 8y ago> Nobody reasonable serves up different content on the two URLs. The third and ninth comments in the linked bug present real world examples of this behavior.
- nimrod0 8y agoYes, why not drop URL's altogether then? Why display such "technical" things for the plebes?
- type0 8y agoSure, "I'm feeling lucky!" should suffice /s
- r3bl 8y ago> Most sites are on .com domains after all. Most sites in English, and even that is doubtful. There's a full world out there of people and businesses using ccTLD like .fr, .nl, .co.uk, .hr, .rs, .es, .jp...
- uberman 8y agoWith "only" 46.5% of all domains being ".com" I guess you are technically correct. When the next highest TDL (.org) rings in at only 5.1%, I think we can agree the the overwhelming majority of sites are based on .com. Of the TDL you mention the top one is .jp at less than 2%. If you remove the qualifier under the .uk TLD you get an additional 2%. The rest don't make the chart. https://www.statista.com/statistics/265677/number-of-internet-top-level-domains-worldwide/ https://www.statista.com/statistics/265677/number-of-interne...
- dan-robertson 8y agoAs I recall, there are some reasonable dns-related reasons that one might prefer www (or any subdomain) to the bare name.
- dfox 8y agoModern solution to these issues is having SRV record on appropriate protocol sub-domain which AFAIK (and somewhat surprisingly) is honored by most modern browsers.
- dragonwriter 8y ago> If I were solving this, I'd instead push to eliminate "www" altogether, not sweep it under the rug. It was useful circa 1996, when users might plausibly be using something other than the WWW with a browser. No, it was useful when abstracting machine identity from domain names such that there was a many-to-many relationship was less common, so “www” was the most specific domain name element for the server being accessed. (And a system that needed more than one server might have a homepage on “www”, and various subsites and apps on “www1”, “www2”, etc.) OTOH, there may be places that still allocate servers that way for simplicity.