From a technical perspective, littering your URLs with implementation debris is not a good idea. What if you want to revamp the site, put it in a shiny CMS, and now it's in PHP or JSP or does it even matter? You have all these references to `index.html` you have to maintain or you'll be wrecking your linkage.
Bury those. If you're doing a plain HTML site, use MultiViews to hide the extensions. They're not important to the content.
When I see `index.html` in a URL, it's never a good sign. It's done by a sloppy "web designer" that knows how to use DreamWeaver and FTP things to the server. They make a tremendous mess for the next team that has to come along and somehow upgrade the site without breaking everything.
It's not 1998 any more. You can afford to script your pages, have clean URLs, and still get great performance.
Bury those. If you're doing a plain HTML site, use MultiViews to hide the extensions. They're not important to the content.
When I see `index.html` in a URL, it's never a good sign. It's done by a sloppy "web designer" that knows how to use DreamWeaver and FTP things to the server. They make a tremendous mess for the next team that has to come along and somehow upgrade the site without breaking everything.
It's not 1998 any more. You can afford to script your pages, have clean URLs, and still get great performance.