I have no idea why some think it's a good idea to 'supplement' the browser's built in navigation by overriding yet more of its standard keys. On pressing left arrow, I expect it to behave uniformly, not navigate to some other page. If you insist on doing this, then at least use accesskeys= attribute. Instead I'm left reeling, hands off, staring at my keyboard as if it is an unknown enemy preparing to attack.

Really don't care about presentation (serve your blog in text/plain all I care), but some things are unforgivable. Didn't get reading past the first few lines.

Is it really unfair to assume someone who makes this mistake could not hold any kind of useful, complex, technically valid opinion that would teach me something new?

Surely there is a name for this phenomena.

Just like human languages have more than one word for the same thing (words for sex, genitals, alcohol, people you like/love/hate).

When something is popular (like the things I mentioned above) words to describe it flourish.

Also, the url is a close to a universal thing as we have in programming. Almost every framework evolves to eventually deal with a URL (Greenspun's Tenth Rule).

So maybe this is asking why the word for (sex|drugs|etc) are different in English than Russian.

</wild speculation>

Yet another lovely cheatsheet to print off and hang on the wall by my desk. Thank you remi. Perhaps I should put up a blog post with all my cheat sheets some day.

I was somewhat disappointed that the author of this article left out URI "path parameters": semicolon-delimited name/value pairs that can be attached to each component of the slash-delimited path.

I see the block at the end as "

A few conclusions: "/* is more prevalent than "/. Yet anecdotally developers use "/ more, and in practice most schemes are protocols. "/* is used consistently (to mean the same thing) as are "/* and "/. "/ has been used consistently for the past 10+ years and in a way consistent with its operating system roots. "/* is used inconsistently as to whether or not it includes the leading "#" hash/pound symbol. However, notably absent from any specification or platform was the alternative phrase "/*.

"

I feel there is something wrong

And absolutely any combination gets named "baseUrl".

I've seen people confuse "http" with "http:", as in "the 'http:' URI scheme".

The name of the scheme is "http"; "http:" is meaningless.