|
|
|
|
|
by chrisBob
4409 days ago
|
|
Long URLs hurt the user experience and destroy the Web. If I want to send you a link to a washingtonpost.com article the link looks like:http://www.washingtonpost.com/opinions/ej-dionne-jr-the-root... The same url could just as easily be user readable, and something that I could tell me office-mate verbally from 10 feet away. Most people just expect bad URLs now and have given up trying to remember the name of the page they want to see. I used to love NBC.com because they would let me type things like nbc.com/parks to get to http://www.nbc.com/parks-and-recreation, but that is no longer true. Now everyone just assumes that they need to google something to find it, and they can't even imagine that apple.com/ipad would be the page they are looking for. |
|
apple.com/ipad is a good URL because it describes the destination. so is nbc.com/parks. but there is a practical limitation to that sort of url scheme - you only get a couple hundred pages max before you exhaust your namespace. you couldn't use a URL like that for every single article a newspaper writes without an absurd number of collisions. so you have to start using unique IDs. and if you only use the ID, you lose the memorable/describable aspect.