We develop a lot of UK government web-sites and accessibility is a major issue.  That is, could this site be used by someone who is blind, can't use a mouse or keyboard, has some form of special browser that does not support Javascript.

Remember also that someone can switch Javascript off in normal browsers.

For this reason we either don't use client side Javascript, or provide <NOSCRIPT> alternatives.  We tend to favour the former because developing client side Javascript means doubling of effort as we have to provide the <NOSCRIPT> alternative in any case.

On the performance front we find that sites that work fine with a few thousand users fall to bits when a few tens or thousands of users hit them.

I've said it many times on SQLServerCentral, this is A solution not THE solution.  If your solution works and can cope with the site traffic you have and the site audience then you have produced successful code.

There is another aspect to this which I merely hinted at in my article.  By shifting the complicated stuff onto the database server I am making the programmers task a lot easier and for that they are extremely grateful. 

Their appreciation manifests itself in lots of ways, in order of priority

• Free beer.
• They get me involved at the design stage.
• They ask for their SQL to be vetted.
• They preach stored procedures with the zeal of the converted.

OK, it increases my workload, but that is what I get paid for!