It also checks its JavaScript

This site does make (fairly heavy) use of JavaScript. It attempts to do it in a transparent and generally nice way, so as to not impede the progress of non-JavaScript aware browsers, or people who don’t like client-side scripting. You should also not be seriously inconvenienced when viewing this site without JavaScript, since the features that it adds are merely aids to navigation (or pointless chrome, depending on who you talk to :-) With regards to colour schemes, the images and colours should degrade sufficiently down to 256 colours without a problem at all. I’m not sure what they will look like in 16 colours; possibly horrible. If they do, I apologise. This site uses (as far as I know) no browser specific tags. It also checks its JavaScript; it should work fine in IE3 and Netscape 2 as well as higher versions by degrading its JavaScript calls through different versions, and, as mentioned above, JavaScript is not required for anything on the site. I did, at one point, consider having differing versions of this site; one for JavaScript aware browsers, and one not. However, that means mirroring information, unless you deprive the low-bandwidth people of some of the information that is available in the other site, and that defeats the object entirely. So, this site, as mentioned above, degrades well (I believe). If there’s one thing I really dislike, it’s seeing the phrase “This site best viewed with” or “is required to view this site” somewhere on a web page. Now, I’m the first to admit that there may be problems with this site about which I do not know; I’m not being deliberately hypocritical. (If you find that there’s a problem with displaying some aspect of this site, I’d appreciate it if you could email me and tell me about it; the address is on the personal page.) But optimising your site with IE or Netscape specific features, like (say) floating frames, or JavaScript 1.3, is a poor showing indeed. I have no objections to people who want to only make a feature available to (say) Netscape users, but please, please use JavaScript, or an Active Server Page, or a CGI script, to check your viewer’s browser and transparently offer it to them. Don’t tell me that I’m missing features, just because I haven’t got the latest version of the latest browser; just show me everything I need to see. And don’t, especially don’t, make navigation or use of your site depend on these ‘optional’ features!

Written by me. In 1997.

I still don’t think that use of your site should depend on JavaScript.

You probably don’t have to use ASP any more, though.

I'm currently available for hire, to help you plan, architect, and build new systems, and for technical writing and articles. You can take a look at some projects I've worked on and some of my writing. If you'd like to talk about your upcoming project, do get in touch.

More in the discussion (powered by webmentions)

  • John OK responded at reposts this. ( RT @sil: Quite pleased with…. I occasionally had the right idea :)
  • Ironhack responded at likes this. (
  • Simon Mackie responded at likes this. (
  • Sturm Flut responded at likes this. (
  • Joshua Hoover responded at likes this. (
  • Paul Tibbetts responded at likes this. (
  • Paul Freeman responded at likes this. (
  • Aaron Gustafson responded at It Also... ( Stuart Langridge has been writing smart JavaScript for the last 18 years. We should all be that pragmatic. Read on As Days Pass By
  • Ṱṝⱥⱴ Ṧṫộṉề responded at @AaronGustafson … Or else it gets the hose again? #SilenceOfTheLambdas
  • Stuart Langridge responded at likes this. (
  • Javascript Digest responded at reposts this. ( RT @AaronGustafson: It also checks its JavaScript…
  • ★ jen strickland ★ responded at likes this. (
  • Simon Willison responded at