I agree with MoGryph. OO Js not only isn't that hard, as Jake has found, once you get into it, and reusable (code once use often), Client side JS is a courtesy to the user. Would you rather wait for a form to submit and then get a page returned to you with modifications or some other alert telling you where the error are (most shopping forms online come to mind) or would you rather know about input miistakes as each field is completed?
There are some great arguments for making the UI nicer, especially where not frustrating the user could be the difference between a new customer and lost business.
I do agree with GM though that you do need server side validation for the stated reason that you can get 'round JS validation if you want to.
I think this conversation has happened already in the past here on Codestore... the gist being do both. Client for the customer, server for the data.
I agree with MoGryph. OO Js not only isn't that hard, as Jake has found, once you get into it, and reusable (code once use often), Client side JS is a courtesy to the user. Would you rather wait for a form to submit and then get a page returned to you with modifications or some other alert telling you where the error are (most shopping forms online come to mind) or would you rather know about input miistakes as each field is completed?
There are some great arguments for making the UI nicer, especially where not frustrating the user could be the difference between a new customer and lost business.
I do agree with GM though that you do need server side validation for the stated reason that you can get 'round JS validation if you want to.
I think this conversation has happened already in the past here on Codestore... the gist being do both. Client for the customer, server for the data.