your guess? when i devlelop intranets/extranets i use javascript because the
client can tell its employees/partners what the requirements are for using a
given web-based applicaton. however, when i develop publicly accessed sites
i don't rely on javascript. the reason is it can be turned off, not whether
i guess at how many people have/leave it turned on. the sites i build and
maintain generally have moderately high traffic and inevitably there are
people who write in and say "this didn't work" or "why did this happen". it
depends on the scope of work and who the audience is. but if your audience
is big enough, you'll get feedback here and there by not conforming to a low
common denominator with respect to browser capabilities.
i'm not saying you're doing it right or wrong, but i am saying you shouldn't
blatantly dismiss it as a development methodology.
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 18, 2001 5:15 AM
To: CF-Talk
Subject: Adam, you got to be kidding?
You actually develop with the mindset that a user might not have scripting
enabled? Ouch!
My guess would be that at a minimum, 98% of all users have scripting
enabled.
So, you would forfeit the capability of client-side data validation,
client-side DOM manipulation, etc.?
You would add unneeded round trips to your server to accomplish scripting,
validation, etc.? So 98% of your users will pay the Performance price for
the
2% of your users? Not to mention the extra load on your server and the
wasted
bandwidth.
Not a good idea ... Please!
Bill Reichard
Willow Gold
[EMAIL PROTECTED]
http://www.willowgold.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
