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 JS. The user experience is definitely enhanced from the use of client side JS (it was a kind of online spread sheet used by the finance dept), but it's nothing I couldn't have done, with a little work, on the server side (and *lots* of page submissions). On Mon, Jun 15, 2009 at 4:29 PM, raven<rav...@mail.ru> wrote: > 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 > support js. > Another question that i try to keep all of them, if it's possible. > >>Graceful degradation is better than nothing, but progressive enhancement >>rocks. > ACK. It rocks. > Problem: > Often some js feature (AJAX for example) is key to the project. > Than first i develop server side scripts and front end, which depends on AJAX. > And after i finish, if there is enough time and budget is OK, i modify front > end (if needed) and write additional server side scripts so user may work > without js. > If code is good — add such accessibility feature is not a problem. > But if you get project with low budget and where deadline was yesterday, than > accessibility must first be sacrificed. If project stay alive — you may > return to this question. > Yes, progressive enhancement rocks. But, if don't use it wisely, you'll > starve. > >>Also I do support witches, but that's off-topic. > Sorry for my English. I need more practice. Much much more practice. :) > > Regards. > Raven aka Silent Imp. > > > ******************************************************************* > List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm > Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm > Help: memberh...@webstandardsgroup.org > ******************************************************************* > > ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org *******************************************************************
