3 ms·
You're in good company. Tim Berners-Less said something similar when reflecting on what he would do differently if given the chance: > Looking back on 15 years
by travem 8y ago
You're in good company. Tim Berners-Less said something similar when reflecting on what he would do differently if given the chance:
> Looking back on 15 years or so of development of the Web is there anything you would do differently given the chance?
> "I would have skipped on the double slash - there’s no need for it. Also I would have put the domain name in the reverse order - in order of size so, for example, the BCS address would read: http:/uk.org.bcs/members. The last two terms of this example could both be servers if necessary."
From http://www.impactlab.net/2006/03/25/interview-with-tim-berners-lee/ http://www.impactlab.net/2006/03/25/interview-with-tim-berne...
- nathan_long 8y agoYes. Think how you have to read "mobile.tasty.noodles.com/italian/fettuccine" to determine where it goes. First start at the slash and work your way left: "com -> noodles -> tasty -> mobile" - then jump back to the slash and work your way right: "italian -> fettuccine". This is counterintuitive and I doubt most users understand it. "com.noodles.tasty.mobile/italian/fettuccine" makes more sense to me. Also, I think TLDs like "com" and "edu" and now "io" and "cool", etc, are misguided. I wish we had "country.language" as the only TLDs. For instance, "us.en.apple.www/mac". I see several advantages. One, if "us.en.apple" and "uk.en.apple" were different entities, it would make legal sense, whereas "apple.com" and "apple.cool" being different entities makes no sense. Two, a use would likely notice if they ventured outside their usual TLD(s), and be less surprised by the different entity. Three, these TLDs could have rules about allowed characters; eg, only ASCII in "us.en". This would make homoglpyh attacks much more difficult.