|
|
Posted by David Segall on 11/20/07 11:39
Stan McCann <me@stanmccann.us> wrote:
>Andy Dingley <dingbat@codesmiths.com> wrote in
>news:spfnu154l3vj60ilocq9mbatjenjmlqpc9@4ax.com:
>
>> How it does it is that it breaks the old HTML dependence on HTTP,
>> and a single "get page, submit page, get page, submit page"
>
>Sorry, that's the way the web was designed to work.
>
>> sequence. Bits of JavaScript code and a component that can retrieve
>
>Which is a good enough reason not to use it. You run your programs on
>your computer; I will run my programs on my computer. And if I don't
>know you, or I've never seen any information about your program; I damn
>sure ain't going to run it on my computer.
>
>Client side scripting is, and has always been a bad idea. If it were
>more limited on what it could do on someone elses computer, ok, but I
>don't want my window resized, I don't want you to take away all the
>buttons on the window that I am familiar with and know how to use so
>that you can put some buttons in place that I don't know how to use.
>
>Javascript is always off until I know what a page author wants to do
>with it (IF I bother to look or care).
Casual users do not need a rich client and there is usually no
justification in complicating a web application for them. However, for
sovereign applications the usual web interface is worse than useless.
Imagine spending all day using a spreadsheet program that required a
"Submit" every time you wanted to see your changes. Ajax is just the
current fashion in the attempt to merge the advantages of web based
applications with the features of desktop ones.
Navigation:
[Reply to this message]
|