4 ms·

(Just to clarify...) I know what you mean, but I don't think your question makes sense without comparing it to something. That something would naturally be the

(Just to clarify...) I know what you mean, but I don't think your question makes sense without comparing it to something. That something would naturally be the path. www.google.com makes as much sense as com.google.www but www.google.com/root/sub/subsub makes less sense than com.google.www/root/sub/subsub or subsub/sub/root/www.google.com Since the latter has consistent increasing or decreasing of specificity, while the former has not. This incidentally mirrors what I don't like about the date format MM/DD/YY.

gabriel-coarna 17y ago
Actually, com.google.www/root/sub/subsub would make the most sense. The Commercial domain. The Google host/company. The www service/sub-domain. The path.
- pwmanagerdied 17y ago
  I don't think that there's anything inherently more sensible about going from least to most specific instead of the opposite, as long as it's consistent.
riobard 17y ago
That's exactly what is in my mind! The mismatch of domain name order and path order really bothers me for a while and I just couldn't find a sound reason for that. For the date format, AFAIK, only English speaking countries use MM/DD/YY, possibly due to the same order in plain writing style, e.g. October 17, 2009. This is completely insane for virtually other parts of the world because logically it's either YY/MM/DD (big to small) or DD/MM/YY (small to big), but NEVER MIXED!
- etherealG 17y ago
  actually, only USA does the rediculous MM/DD/YY. the UK is DD/MM/YY
  - pbhjpbhj 17y ago
    Plus when saying a date it is usual to say the day first in the UK then the month if it's not clear from context. The US date ordering is one of those things (like non-metric units) that make me feel that they're being purposefully obstructive; kinda like Microsoft, always avoiding using other peoples agreed standards.
  - deleted 17y ago
    [deleted]
jacquesm 17y ago
The added disadvantage of the current scheme is that it allows all kinds of phishing tricks that would have been a lot harder to get away with if the domain elements would be in the reverse order. htp://twitter.com.someidiotdomain.info/enteryourpaswordhere would stand out immediately. (only one 't' so HN doesn't turn it into a link).

gabriel-coarna 17y ago

Actually, com.google.www/root/sub/subsub would make the most sense. The Commercial domain. The Google host/company. The www service/sub-domain. The path.

pwmanagerdied 17y ago
I don't think that there's anything inherently more sensible about going from least to most specific instead of the opposite, as long as it's consistent.

riobard 17y ago

That's exactly what is in my mind! The mismatch of domain name order and path order really bothers me for a while and I just couldn't find a sound reason for that. For the date format, AFAIK, only English speaking countries use MM/DD/YY, possibly due to the same order in plain writing style, e.g. October 17, 2009. This is completely insane for virtually other parts of the world because logically it's either YY/MM/DD (big to small) or DD/MM/YY (small to big), but NEVER MIXED!

etherealG 17y ago
actually, only USA does the rediculous MM/DD/YY. the UK is DD/MM/YY
- pbhjpbhj 17y ago
  Plus when saying a date it is usual to say the day first in the UK then the month if it's not clear from context. The US date ordering is one of those things (like non-metric units) that make me feel that they're being purposefully obstructive; kinda like Microsoft, always avoiding using other peoples agreed standards.
- deleted 17y ago
  [deleted]

jacquesm 17y ago

The added disadvantage of the current scheme is that it allows all kinds of phishing tricks that would have been a lot harder to get away with if the domain elements would be in the reverse order. htp://twitter.com.someidiotdomain.info/enteryourpaswordhere would stand out immediately. (only one 't' so HN doesn't turn it into a link).