[Sigia-l] "Who Really Turns Off JavaScript?"

[Timothy Karsjens]

 -------- Original Message --------
> From: Listera <listera at rcn.com>
> I think JS has stopped being an "issue" long time ago.
> ---- 
> Ziya

I think that it is not the case that it is an issue, so much as whether or not you want to build something that works 100% of the time, versus something that works 85% of the time.

Me, I would prefer to build something that works 100% of the time, as long as the application servers are up.

You mentioned complexity on the back-end...  Nearly all of the developers I have worked with on web applications will tell you that if there is any functionality in JavaScript it will make the back-end MORE complex rather than less.  Using JavaScript to even validate a form is a ridiculous waste of time if you are building a real application.  Why?  The form data is going to be validated AGAIN on the back-end anyway.  Using JavaScript to do anything of importance in an application is just bad, in my opinion.  There are too many cases (15%!!!) that would keep me up at night.

Maybe I *am* too much of a perfectionist, but based on the current browser stat captures out there, that 15% is just unacceptable.  If that application server is up, my functionality better be running at 100% across the board, not 85%. Wow,  I think I *may* be a perfectionist.  Looking back at the previous project I mentioned, with 5000 functional JSP modules... In the year and a half I was on the project, I only had 5 QA bugs, total, all of which were low severity word wrap issues.  Since I was the only one touching the UI, well... I guess my epiphany for the day is that I should *embrace* the perfectionism.

*grins*

Oh, and *gasp*, it was an AGILE METHODS project, too...

--timothy karsjens