The www in front of urls should have been made obsolete about twenty years ago. For that length of time almost all sites have mapped to the same place whether it’s specified or not.
Pretty easy to do but I wouldnt say it is obsolete. WWW tells you what type of site it is. just like m.whatever.com says its a mobile website. FTP.whatever.com tells you its a ftp site. There are others. The reason why www.fathom.org doesnt work is because it is not WWW it is FFF
It is extremely easy to do. It is one line of data in the .hosts file, if my memory is right. I recall screwing up a couple in my day, but unless there is a compelling reason, I would default to domain.com going to the website.
Yes, back in the day, it was very useful to have ftp., www. or mail. in front of things so you knew what you were doing. However, I don’t much see the point any more.
The kallback sites both go to the same place for me. It depends on your host as well. Some automatically fix it so your names go to the same place.
Some people are afraid to change this, cause Google will treat the page rank seperately of a www.example.com vs example.com
Though a 301 redirect should be OK, they don’t want to take a chance.
The real problem is browsers are so good at fixing people’s programming errors we have no incentive to make the webpages correct in the first place. That’s a pet peeve of mine. When I make a site I always use XHTML strict and validate it. Most places don’t even care, 'cause they know the browser will fix it.
Setting up the www subdomain is not a coding or a scripting thing. Yes, the lack of the subdomain can be FIXED with coding/scripting but the host is responsible for setting up the www subdomain in DNS and also in the web server (such as IIS or Apache).
But this is by convention of practice only, not necessary technically. I could have an ftp site on a www server if I wanted to. I could have a web server, SMTP server, and ftp server all running on the same machine with no prefix at all (there are conventions for which ports are used for these, but that’s convention too).
Either I am misunderstanding you or I think this is incorrect.
WWW is not the equivalent/alternative to FTP. FTP is the protocol and the equivalent/alternative is HTTP. WWW denotes the server and can be any protocol.
As others have said, it is pretty easy for make both www.<domain>. and <domain>. point to the same place. The www is administrative convention so we sysadmins don’t have to stare at a DNS record and guess what the record is for. You could assign your web server to ftp.<domain>. and your ftp server to www.<domain>. if you wanted, but you’d annoy your techs.
Historically, <domain>. A records have been used for lots of different purposes: web servers, mail servers, authoritative DNS servers, etc…, so having the naming conventions eases administrative burdens.
Right. It’s solely for us humans: Computers distinguish by assigning different port numbers to different services, which is also merely a convention but it’s enforced by software to a much larger degree.
There is no reason to keep using the www prefix: The Web won as far as mindshare is concerned, so it gets to be the default and prefixes, if they are used at all, should only be used for secondary services such as FTP, Gopher, SSH, and so on.
I think those guys have the right idea: the “www” is as obsolete as typing “http://” in front of every url.
I tested my own sites, provided by free online services, and got a Class A rating, something I can put into a homemade certificate and frame! Won’t my grandchildren be impressed!