Actually the question is not whether I should use javascript, but whether I should actually spend the time and effort making the application work without it. I want to be considerate of the blind, but on the otherhand I'm not sure if I'm putting too much effort into that. Maybe I should build the ajax version first, launch, and then start building a verion that works without. I use noscript but have a liberal allow at first loss of functionality policy.<p>note: I really think the non-js version of my site is going to be cludgy<p>so how important is having a non-js version to you?
Depends what you're making. Some sites just plain don't make sense without JavaScript, eg. Meebo. But if you're not one of them, you'll have a much better site all-around by using progressive enhancement. Build the site without JavaScript first, and then gradually layer JavaScript on top to improve usability problems caused by its lack.
The use of js varies so much from site to site that noscript can mean very different things to the user experience. I would say that in the majority of cases, js provides an extra layer of smoothness. With this, disabling it should not make functionality disappear.
Javascript support is pretty strong today. Browsers keep optimizing JS and JS is obviously quite powerful. I don't see a reason why you would not use it other then the fact its just tedious at times.