Then browser TLD defaulting would have handled most cases and we could have had additional conventions (such as *.store). (The "www." subdomain is basically useless.)
Then browser TLD defaulting would have handled most cases and we could have had additional conventions (such as *.store). (The "www." subdomain is basically useless.)
The web has no hierarchy so it doesn't make sense for domain names to have one. It would have been nicer to ditch the TLDs, use a sane protocol name and have implicit slashes. Like web:disney/some-path.
www.group.department.university.edu.country/person/topic/page
Instead of the more logical
country.edu.university.department.group.person.topic.page
Actually, the "web" does have lots of hierarchy.
For example, Disney has hierarchy that the current scheme makes it inconveient to express. That's why we have disneystore.com, disneycruise.com, etc. instead of com.disney.store, com,disney.cruise, etc.
Tanguy Ortolo answers 'Why www?' better than me.
The same as today.
In www.disney.com, disney controls that www. In com.disney.wwww, disney controls that www.
However, in the latter, disney could do com.disney.store . And, with browser defaulting the tld, disney.store would work.
Disney isn't going to use store.disney. However, they might well use disney.store if they controlled it. With the current order, they don't. They would with the reverse order.