Hi.
If a website client of yours hired
you to manage an actual storefront and you
arbitrarily slammed the door in the face of every
100th, 200th, or even 1000th customer, how long
do you think would you keep your job?
If some js feature bring me 100 costumers i can effort loose 1, which don't
Out of curiosity, what sort of feature are you talking about that
can't be done server side (ie, *without* AJAX)?
I'll confess to relying heavily on server side JS on some projects,
but I did so because I knew those apps would be used exclusively on an
intranet where the SOE was known to support
I think the point is if you should be spending time developing
something with a bad user experience that hardly anyone will use. Yes
you could implement a spreadsheet app with tons of page requests, but
the user experience would be so bad that people probably wouldn't want
to use it.
On
Hi.
Out of curiosity, what sort of feature are you talking about that
can't be done server side (ie, *without* AJAX)?
As a matter of fact, you right.
Without AJAX (in any form) server side scripting remains intact and matter
disappears.
My front end development order:
1. XHTML coding of
At 6/14/2009 11:28 AM, raven wrote:
Keep in mind as always that a JavaScript solution will not work in
user agents not running JavaScript,
which can include search engines,
mobile devices, assistive technology, browsers in certain corporate
contexts in which JavaScript is globally turned off
