> I don't understand why it's there. It's a bit redundant given all the arguments of the no-www folks. I agree. It's redundant and, like 'http:// http://, can

> I don't understand why it's there. It's a bit redundant given all the arguments of the no-www folks. I agree. It's redundant and, like 'http:// http://, can and should be inferred. I also think it looks much better without it. The reason it won't go away is technical. See Heroku's article on it: https://devcenter.heroku.com/articles/avoiding-naked-domains-dns-arecords https://devcenter.heroku.com/articles/avoiding-naked-domains... I do hope that the technical reasons for not using naked domains can be worked around some day. Whether by evolution of the technology or by the browser inferring it.