Forum Moderators: open
No More WWW
I'm through with it and good riddance!
2008-01-06 - [webmasterworld.com...]
I do believe I'll have a little more support this time around for my No More campaign. And, I won't be changing my mind after 20 replies either!
So, what are the Pros vs. Cons of going Extensionless? Are there any added usability and accessibility benefits?
Have you stripped yet?
Not sure there is any added benefits other than "beauty factor".
Ah, but I do believe there are many "added benefits" in addition to the beauty factor as you say. I've followed a few large Internet properties that utilize Extensionless URIs, two of which are the W3 and Google. I've done quite a bit of research within those domains picking apart the taxonomy and how it all works. I really dig Extensionless.
And what happens when you have two (or more) files with the same name but different extensions?
I don't know...
You'd have to use the extensions anyway. Seems like something not worth it to me.
Those extensions are just one of many different areas that one can focus on to "lock things down" as they say. In reading a bit of server security information, the Extensionless protocol (Content Negotiation) is "one" of many suggestions in an entire "protection" package. I know, maybe not worth the time and effort just for "visible" protection. But it really does go a bit deeper than that.
Also, since Yahoo! and Live want to continue to strip away trailing forward slashes in their Display URIs, I'm going to give them what they want!
With an extensionless URL system in place, the update is purely internal to the server.
The other advantages, although possibly minor, are still real: Shorter URLs save bytes, reduce load time, and are easier to type in and remember (eliminating the .html/asp/php extensions has advantages similar to that of AOL 'keywords' in ease-of-use).
Jim
Vert smart, didn't think of this. Thanks for that, Jim. It might be worth going extentionless just for this added benefit.
But where pages are concerned, the extension is not needed -- No-one cares if our pages are .html, .htm, .shtml, .shtm, .php, .asp, .xhtml, or .whatever or how they are produced (static vs. dynamic).
Jim
Regular user may not care, but what if web browsers won't care either by stripping domain extension and diluting/limiting branding potential (but it may be a new topic).
What about graphic or video files like .gif, .png, .jpg, .wmv, .rm, .swv and several others. Is it possible to present them with no extension (what about usability/possible confusion)?
What about graphic or video files like .gif, .png, .jpg, .wmv, .rm, .swv and several others. Is it possible to present them with no extension (what about usability/possible confusion)?
It's possible if you put each file type in a different folder and then use your URL rewriting technology to deal with it.
Wouldn't that be the same as using extensions, except that the file type is replaced by the folder name? You don't really gain much except more complexity in URL rewriting.
What if you have two versions of a file, e.g. .doc and .pdf? Intuitively, i'd refer to them as //example.com/files/blah.doc and //example.com/files/blah.pdf. It makes it obvious what kind of file it is, especially when someone sends you a link by email. It might also make it easier for some search engines to figure out that they're different versions of the same content.
The point about replacing extensions like .php, .asp, etc by .html is very valid. In reality, the produced content is not php/asp anyway but html and it should be identified as such.
The other advantages, although possibly minor, are still real: Shorter URLs ... are easier to type in and remember
How often do people type in URLs other than the domain name, possibly followed by one "folder" name? Anything more complicated than that, and i'd guess nobody would bother to remember, or at best they'll try the URL without and with a .htm/.html extension until one works.
Wouldn't that be the same as using extensions, except that the file type is replaced by the folder name? You don't really gain much except more complexity in URL rewriting.
I would not remove extensions for images.
That is, a page of HTML code will always be a page of HTML code, whatever the extension, whereas an image could be a JPEG, PNG, GIF or something else, and the extension conveys meaning.