Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

That's just because you are used to it. But <tld>.<domain> actually makes more sense for multiple reasons:

- That's how phone numbers work, the most significant part of the number is first (<country-code> <area-code> <local-number>) so the most significant part (TLD) should come first in domain names. Users like systems that look like other systems they are already used to.

- <tld>.<domain> would help thwart phishing attacks as most users read left-to-right, so they see right away when the domain is incorrect. Compare this to "google.com.phishing.com" which tricks users because they stop reading after they see "google.com..."

- When you read or hear "go to com.myawesomedomain" you know a domain name is being mentioned as soon as you hear "com.". It is not always obvious otherwise (you have to use specific language like "browse to").



If it was com.something you have to type the com first. If "something" is first, you by the time you get to "som" it will probably have something.com in the dropdown list.

I would say its easiest if the most variable part is first, not only for autofill but for the way I think about it.

When you talk about "most significant" you mean the "largest" category. To me the actual most significant is the part that identifies the most unique thing you are typing in, and that tends to be the domain.


Modern web browsers will complete from any start position in an URL (and some also from the title of the document, I think). E.g. if I have visited the Wikipedia article on irish setters and I start typing irish, it will suggest that article. In the same fashion, if the URL was com.example and you typed exa, it should suggest com.example.


That's also how your filesystem works, and a little bit of similarity with something that is already well understood can only help.


Saying the brand first definitely make more sense to mere mortals. Phone numbers not a good comparison because they are...numbers, not brand names.


Once again, you say that because you're used to it. When you go to a store, do you go to the item first, then figure out what section it's in then figure out what isle it's on?


No, but when you're looking for a particular website, you Goggle it, then check domain name is the one you were looking for, by having the name product/company name first, you don't need to scan the superfluous data.


That's true. I can definitely see your point. I think the long story, short here is to stick with what you're used to and by google having .google for domains leaves a bad taste in my mouth.


How about US postal addresses?

<House number> <Street>

<City> <State> <ZIP code>

Except for ZIP code, the address elements are ordered in descending specificity.


Addresses in Japan are written in exactly the opposite order, with the post code being written at the top of envelope followed by the prefecture, state, etc. Its simply what you are used to.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: