I also think that stable URLs are long overdue.<p>I have always felt that file extensions make no sense in web pages.  Why should I, the visitor, need to be dependent on whether or not you &quot;.asp&quot; or &quot;.php&quot; or &quot;.cgi&quot; or &quot;.flavoroftheweek&quot;?  I had a series of bookmarks break entirely because the target site&#x27;s <i>implementation</i> changed.  Fortunately, the site managed to keep all the old root file names so after hacking each bookmarked &quot;&#x2F;filename.foo&quot; into &quot;&#x2F;filename.bar&quot;, I was able to repair them.  (Usually though, that won&#x27;t work at all.  And besides, most people would not even try that, they would assume their bookmarks are lost forever.)<p>For years at past companies, I put up with corporate E-mails containing literally 12 steps of instructions that say &quot;go to company.net&#x2F;portal&quot;, &quot;click X&quot;, &quot;click Y&quot;, &quot;click Z&quot;, and on and on.  Meanwhile I&#x27;m thinking: OR, you could invest in a non-crappy content management system that supports URLs of the form &quot;company.net&#x2F;stable&#x2F;foobar&quot;, allow thousands of employees to click once, go directly to the target and bookmark it forever!  Oh, and of course, the pages would change arbitrarily so it didn&#x27;t even help to save old E-mails with all the instructions.<p>At the very least, <i>tools</i> should support this.  At a previous job, the company overpaid for an &quot;enterprise&quot; bug-tracking system that couldn&#x27;t even provide &quot;company.net&#x2F;bugs&#x2F;123456&quot; for direct-linking to individual bugs, even though this is an obvious case for a stable URL.  Returning to any common issue involved an aggravating series of steps every single time.