[thelist] JavaScript: How much is too much?

Hassan Schroeder hassan at webtuitive.com
Sun Jan 18 16:43:20 CST 2004


Sreedhar Chintalapaty wrote:
>>... you should have as much JS as neccessary 
>>to robustly accomplish the app's purpose.
> 
> Actually, this statement rather proves that the
> question is not without merit. :)

Not if you believe that there's no "typical" app :-)

My preference is to do as much as possible on the server, because
the client environment is essentially unknown -- subject to far
more variables, even in a relatively homogeneous intranet setting.

That said, what are the app's requirements? What is the client
intended to do, how much data is involved, is that data read-only
or read-write, etc.? I think the architecture of each app must be
evaluated individually.

> However, as a programming language, JS provides the
> constructs to do fairly intricate things and in a
> fairly limitless fashion; on a philosophical level,
> one can make the argument that any and all UI-related
> processing should be done on the client (browser, in
> this case) if possible. 

I'm not sure how you're defining "UI-related processing" -- can
you give us an example of your view of what that is/isn't?

-- 
Hassan Schroeder ----------------------------- hassan at webtuitive.com
Webtuitive Design ===  (+1) 408-938-0567   === http://webtuitive.com

                           dream.  code.





More information about the thelist mailing list