URL slash creator: "It seemed like a good idea at the time"
Tons of web design tips.
Tim Berners-Lee, the creator of the Web, says he’s “sorry” for the forward slashes (//) included in every web address. He admits the symbols were actually “unnecessary” and didn’t realize they would be “so much hassle.”
Now that you mention it, those slashes are annoying. Apology accepted nonetheless!
Read the full article.
By Noelle Chun
Comments (9)
Thanks
Viv
Thanks
now, think of all the electrons/energy/ink/etc wasted every time those 11 superfluous characters have been displayed/typed/printed over all these years.
somebody should do a graduate thesis to study the carbon footprint effect of this :)
At this point, there are probably hundreds of thousands or millions of lines of code that account for those // .
As an example, if a program is written to handle a url and then chop off the http:// prefix for aesthetic reasons, if someone changed the standard, the code would break. Router manuafacturers have firmware that looks at traffic and might use the http:// as a protocol identifier. In c#, an absolute URI has the http:// formatting built into the structure of its understanding of what a URI is (and won't validate without it).
Making it optional at this point would likely cause millions of dollars of rework that is unnecessary.
I think we can give the creator of the web a break on this one :)
For instance, when you type <a href="/directory"> in the HTML of a web page, it means that you want 'directory' in the root of your domain. Almost everyone types <a href="http://www.google.com"> to point to Google, but the thing that *is* superfluous in this case, is the protocol handler 'http:', as you are (most likely) already communicating using the HTTP protocol. You can also type <a href="//www.google.com"> to get the same thing and it saves you five bytes. ;)
For instance, when you type <a href="/directory"> in the HTML of a web page, it means that you want 'directory' in the root of your domain. Almost everyone types <a href="http://www.google.com"> to point to Google, but the thing that *is* superfluous in this case, is the protocol handler 'http:', as you are (most likely) already communicating using the HTTP protocol. You can also type <a href="//www.google.com"> to get the same thing and it saves you five bytes. ;)
Leave a comment...