Meh, there was literally never a time when browsers could not technically expand abc.com to www.abc.com to http://abc.com to http://www.abc.com on failure or even by default. Granted, the www...
Meh, there was literally never a time when browsers could not technically expand abc.com to www.abc.com to http://abc.com to http://www.abc.com on failure or even by default. Granted, the www thing is more complicated, but adding http:// like they do now was never a problem. Just a design choice not to. Because everyone and their mom thought about it.
Microsoft should be sorry instead: for their backslashes.
There totally was! To begin with, it was necessary to specify http, because ftp and gopher were already important protocols, browsers supported all of them, and you couldn't just assume http. And...
To begin with, it was necessary to specify http, because ftp and gopher were already important protocols, browsers supported all of them, and you couldn't just assume http. And it also mattered once https arrived.
And it took a while for www to be the generally accepted prefix. There were websites that had web in place of www, and http://info.cern.ch/ is still up!
Tim B-L was apologizing for the //, which is the bit that's are redundant in an http address. I doubt he'd apologize for the other parts of the address.
Yeah, the backslashes need to go. Why does Windows use backslashes for paths and Unix forward slashes? Personally I think Unix should have used the > key for directories like Multics did, but...
Yeah, the backslashes need to go.
MS-DOS 2.0 introduced \ as the directory separator in the early 1980s. The reason / was not used is that MS-DOS 1.0 (which did not support directories at all) was already using / to introduce command-line options. It took this usage of / from CP/M, which took it from VMS. You can read a more thorough explanation of why that choice was made on Larry Osterman's blog (MS-DOS even briefly had an option to change the option character to - and the directory separator to /, but it didn't stick).
But without them I will have missed all the memories of watching PBS shows telling me to go to “aich tee tee pee colon forward slash forward slash pee bee ess dot com”.
But without them I will have missed all the memories of watching PBS shows telling me to go to “aich tee tee pee colon forward slash forward slash pee bee ess dot com”.
That’s because the letter W used to be shorthand for “uu”. The reason why it is shaped sharply in many fonts is because some languages, like German and French, it’s short for “vv”.
That’s because the letter W used to be shorthand for “uu”. The reason why it is shaped sharply in many fonts is because some languages, like German and French, it’s short for “vv”.
Is it weirder to see that character and pronounce it with the “vee” sound, or that it literally used to be the character used to show the more vowely “oo” or “wu” sound, like it was used in Roman...
Is it weirder to see that character and pronounce it with the “vee” sound, or that it literally used to be the character used to show the more vowely “oo” or “wu” sound, like it was used in Roman times…
Because it has a completely different feel when talking about the destruction caused by the “Mount Wesuwius” eruption…
A decent (as much as Slashdot can be from 2009...) thread on this. But, it did give way to that amazing Moz://a logo, so I'll say it was worth it just for that. If you type that out in Firefox it...
"'Look at all the paper and trees, he said, that could have been saved if people had not had to write or type out those slashes on paper over the years — not to mention the human labor and time spent typing those two keystrokes countless millions of times in browser address boxes." - A quote from the interview on this.
A decent (as much as Slashdot can be from 2009...) thread on this.
But, it did give way to that amazing Moz://a logo, so I'll say it was worth it just for that. If you type that out in Firefox it will redirect you to the manifesto.
The name "Slashdot" came from a somewhat "obnoxious parody of a URL" – when Malda registered the domain, he desired to make a name that was "silly and unpronounceable" – try pronouncing out, 'h-t-t-p-colon-slash-slash-slashdot-dot-org'".[15]
And CmdrTaco (Rob Malda) would actively campaign against people using "The Cursed WWW" when linking to Slashdot, because the joke doesn't work as well for http://www.slashdot.org.
And CmdrTaco (Rob Malda) would actively campaign against people using "The Cursed WWW" when linking to Slashdot, because the joke doesn't work as well for http://www.slashdot.org.
I suppose we are currently using the double slashes in HTML to indicate a relative URL that starts at the hostname but retains the current protocol. They're not entirely useless!
I suppose we are currently using the double slashes in HTML to indicate a relative URL that starts at the hostname but retains the current protocol. They're not entirely useless!
Discovery is a pretty tough problem because any protocol you design is going to be subject to malicious actors (e.g. people trying to win elections, or even just people trying to push their...
Discovery is a pretty tough problem because any protocol you design is going to be subject to malicious actors (e.g. people trying to win elections, or even just people trying to push their low-quality spam) and has to resist them.
Of course, that's not to say that it's not possible. I'm just not sure you can "solve" it in the same way that you can "solve" the transmission of documents using HTTP.
He should’ve used ~~ I guess. It does seem reasonable that http: should’ve been sufficient (like mailto:). It’s a shame the article didn’t ask him why, but it seems to be answers here:...
He should’ve used ~~ I guess. It does seem reasonable that http: should’ve been sufficient (like mailto:). It’s a shame the article didn’t ask him why, but it seems to be answers here: https://www.w3.org/People/Berners-Lee/FAQ.html#etc
Meh, there was literally never a time when browsers could not technically expand
abc.comtowww.abc.comtohttp://abc.comtohttp://www.abc.comon failure or even by default. Granted, thewwwthing is more complicated, but addinghttp://like they do now was never a problem. Just a design choice not to. Because everyone and their mom thought about it.Microsoft should be sorry instead: for their backslashes.
There totally was!
To begin with, it was necessary to specify
http, becauseftpandgopherwere already important protocols, browsers supported all of them, and you couldn't just assume http. And it also mattered oncehttpsarrived.And it took a while for
wwwto be the generally accepted prefix. There were websites that hadwebin place ofwww, and http://info.cern.ch/ is still up!Tim B-L was apologizing for the
//, which is the bit that's are redundant in an http address. I doubt he'd apologize for the other parts of the address.Yeah, the backslashes need to go.
Why does Windows use backslashes for paths and Unix forward slashes?
Personally I think Unix should have used the
>key for directories like Multics did, but that's just me.These days windows respects forward and back slashes so it's not really a big deal.
Except when you're trying to use specific protocols, like SMB/CIFS or FTP, and then it cares very much.
Yes, the backslashes absolutely drive me up the wall!
Modern windows does not care which slash you use
But without them I will have missed all the memories of watching PBS shows telling me to go to “aich tee tee pee colon forward slash forward slash pee bee ess dot com”.
You forgot doubleyou doubleyou doubleyou
That’s because the letter W used to be shorthand for “uu”. The reason why it is shaped sharply in many fonts is because some languages, like German and French, it’s short for “vv”.
So that's why it is called the Svpreme Covrt.
Romans had it right from the first day.
SENATVS POPVLVSQVE ROMANVS
Is it weirder to see that character and pronounce it with the “vee” sound, or that it literally used to be the character used to show the more vowely “oo” or “wu” sound, like it was used in Roman times…
Because it has a completely different feel when talking about the destruction caused by the “Mount Wesuwius” eruption…
A decent (as much as Slashdot can be from 2009...) thread on this.
But, it did give way to that amazing Moz://a logo, so I'll say it was worth it just for that. If you type that out in Firefox it will redirect you to the manifesto.
And, of course, it gave us Slashdot, which if not for the double slash would probably have been named “Colondot”. So thank goodness for that.
surely Slashdot is more from unix than from the web?
Nope, it comes from the url. Quoth wiki:
And CmdrTaco (Rob Malda) would actively campaign against people using "The Cursed WWW" when linking to Slashdot, because the joke doesn't work as well for http://www.slashdot.org.
Kind of amusing in the age where most people haven't even typed "http" in 10 years.
I suppose we are currently using the double slashes in HTML to indicate a relative URL that starts at the hostname but retains the current protocol. They're not entirely useless!
A fun bit of internet history trivia (at least I thought so).
Discovery is a pretty tough problem because any protocol you design is going to be subject to malicious actors (e.g. people trying to win elections, or even just people trying to push their low-quality spam) and has to resist them.
Of course, that's not to say that it's not possible. I'm just not sure you can "solve" it in the same way that you can "solve" the transmission of documents using HTTP.
Aaah really sorry, I totally misread your post, for some reason I thought it said "discovery"!! Yes totally agree.
He should’ve used ~~ I guess. It does seem reasonable that http: should’ve been sufficient (like mailto:). It’s a shame the article didn’t ask him why, but it seems to be answers here: https://www.w3.org/People/Berners-Lee/FAQ.html#etc