6 ms·
> Conclusion: Go with www Am I missing something or is OP using a non-www domain? I'm using Chrome fyi (mentioned because I know safari messes with the address
by update 8y ago
> Conclusion: Go with www
Am I missing something or is OP using a non-www domain? I'm using Chrome fyi (mentioned because I know safari messes with the address bar)
- shapiro92 8y agoyep he defaults without www.
- nasredin 8y agoHis non-WWW site is broken. If you manually append the WWW, the site works. Guess he is Stallmam-serious about practicing what he preaches. Also this is a stupid clickbait non-issue.
- okanesen 8y agoYeah, in the comment section he does state[1], that you should stick with the one you have decided to pick in the first place. [1]: https://bjornjohansen.no/www-or-not#comment-510 https://bjornjohansen.no/www-or-not#comment-510
- consto 8y agoIf you are not using or planning to use sub-domains, the only issue is that you cannot use CNAMEs. This is nearly a non-issue as many DNS providers offer ALIAS/ANAME/ACNAME records that essentially provide CNAMEs on apex-domains.
- admax88q 8y agoChrome messes with the address bar as well.
- amingilani 8y agoOP here, minor nitpick: I'm not the author, I just found something interest and posted it. That said, I agree. The author does jump to conclusions, but that's pretty much why I posted it. It's was first search result and I decided an HN debate would help me find a better answer.
- RKearney 8y agoSafari doesn't mess with my address bar. Chrome on the other hand felt it necessary to remove any instance of www or m anywhere in the domain of the URL before it was rolled back due to backslash. www.m.www.example.www.example.com would show up as example.example.com in Chrome before the rollback.
- Dylan16807 8y agoYou know part of that was a bug, right? And Safari defaults to not even showing 90% of the URL, from what I can find.