I also think that stable URLs are long overdue. I have always felt that file extensions make no sense in web pages. Why should I, the visitor, need to be depe

I also think that stable URLs are long overdue. 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 ".asp" or ".php" or ".cgi" or ".flavoroftheweek"? I had a series of bookmarks break entirely because the target site's implementation changed. Fortunately, the site managed to keep all the old root file names so after hacking each bookmarked "/filename.foo" into "/filename.bar", I was able to repair them. (Usually though, that won't work at all. And besides, most people would not even try that, they would assume their bookmarks are lost forever.) For years at past companies, I put up with corporate E-mails containing literally 12 steps of instructions that say "go to company.net/portal", "click X", "click Y", "click Z", and on and on. Meanwhile I'm thinking: OR, you could invest in a non-crappy content management system that supports URLs of the form "company.net/stable/foobar", 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't even help to save old E-mails with all the instructions. At the very least, tools should support this. At a previous job, the company overpaid for an "enterprise" bug-tracking system that couldn't even provide "company.net/bugs/123456" 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.