[Javascript] Re: Standards

[David T. Lovering]

I would argue that as long as the client machine can do useful work without
burdening the server, more power to it.  If that means letting the user type
in stuff, have it heavily preprocessed, (and maybe defeat the need for submitting
the form at all!), then print out results, etc.,so be it.  After all, JavaScript
and its ilk are programming languages -- we damn well can use them as such!

The whole concept of forms is rather outdated.  The only reason I use forms at all
is because of the fact that most of the input constructs have no existence outside
a form.  I haven't "submitted" a form in about 3 years, and I sure as heck don't
let any form 'execute' on my corporate website.

I am striving for the ultimate in seamless integration between the server-side and
client-side programming languages in which the programmers need not concern themselves
with the issues of interprocess communication between the two platforms, nor need
to be paranoid about the possibility of clear-text parameter exchanges either.  I still
have a ways to go, but I'm about 87% of the way there.

Cold Fusion tried to do this, but it is slow, clunky, has massive overhead, costs a 
kidney, and "doesn't play friendly" with other code constructs.  It also only has about
1% of the combined coding power of PHP, JavaScript, and the like, and the code efficiency 
is extremely poor.  However, it pointed the way -- so I shouldn't be too whiney.

-- Dave Lovering


Jaime Iniesta wrote:
> 
> Cool, but what's the purpose of letting the users type into a web page? Can
> this be submitted with a form or something?