At the risk of sounding rude, you're not building this for yourselves. You're building this for your users. If your users are truly the type of people that freq

At the risk of sounding rude, you're not building this for yourselves. You're building this for your users. If your users are truly the type of people that frequently turn off Javascript in their browsers then by all means; go ahead and do that. But you're going to have to deal with quite a bit of a maintenance burden by making this assumption. Every new feature you add will be "what happens if JS is turned off?". Just leave it on. Assume it's on. If you lose any $ because it's off, compare that to the cost of building and maintaining a JS free application.