A List Apart: Ruining the User Experience
ma.gnolia tags : web 2.0 web design web design tools javascript web development css mac productivity tips tutorials tutorial Design colour theory resources tribal ethnic tibetanjewelry jewelry pagerank alexa stats girls clothing children clothes portfolio web2.0 wiki wissensmanagement socialsoftware Internet culture social software psychology Windows share rounded corners safety passwords aarongustafson webprogramming alistapart
added 2007 Wed Mar 28 7:00:00 by unknown user
Aaron Gustafson (who is a helluva nice guy, and super smart to boot) has a nice piece on ALA which deals largely with sites that require JavaScript. Aaron seems to advocate that one should never *require* JavaScript in their web app, but rather use it only as an enhancement to improve the UI for that visitors with JavaScript enabled (and this, coming from a JavaScript guy). I don't quite agree with Aaron here. I believe there are cases where it's fair to require JavaScript in a web app. We make all kinds of techniqual requirements for desktop apps (you must have *x* amount of RAM, you must have such-and-such video card, etc.) , and I don't see why it should be any different online. That having been said, we should only make these requirements in cases where the app simply isn't possible with them -- which is definitely *not* the case in the examples Aaron uses in the article. Overall, I agree with the sentiment that we should always try to make our apps work without JavaScript. But, I also think there are cases where that simply isn't possible.
Aaron Gustafson (who is a helluva nice guy, and super smart to boot) has a nice piece on ALA which deals largely with sites that require JavaScript. Aaron seems to advocate that one should never *require* JavaScript in their web app, but rather use it only as an enhancement to improve the UI for that visitors with JavaScript enabled (and this, coming from a JavaScript guy). I don't quite agree with Aaron here. I believe there are cases where it's fair to require JavaScript in a web app. We make all kinds of techniqual requirements for desktop apps (you must have *x* amount of RAM, you must have such-and-such video card, etc.) , and I don't see why it should be any different online. That having been said, we should only make these requirements in cases where the app simply isn't possible with them -- which is definitely *not* the case in the examples Aaron uses in the article. Overall, I agree with the sentiment that we should always try to make our apps work without JavaScript. But, I also think there are cases where that simply isn't possible.
