> That’s why it is good practice to not rely on JavaScript, but instead test for it and enhance a markup and page reload based solution when and if the browser was able to load and execute our script. This is called progressive enhancement and it has been around for a long time.

ONLY only for webSITES not for webAPPS. For Webapps I pretend js-disablers don't exist. For something like a blog, news site, etc yes it should work without JS but if one more person tries to tell me to support people with JS turned off in a webapp I'm going to blow. I simply can't be asked to push the envelope AND support people living in the dark ages. This was fine when we just used JS for some client-side validation or the like but now I'm working with drag/drop interfaces, maps, ajax, single-page apps, and more. Those simply DO NOT HAVE non-js fallbacks without writing shit load of duplicate server-side code. Now node.js may offer a way around this (render on the server-side the same templates that are on the client side) but I'm still not sure how you are supposed to replace a auto-complete dropdown for something like tagging friends or just sending a message to a friend on facebook...

If there are enough people to justify making a non-js version then great, here is an IDE, get started, do it yourself I'll even put a link to your site in my noscript tags. I'm past using JS like a little sugar you sprinkle on at the end of a project, it is integral to most of what I write.

Please show me a company (not Google/FB/etc) that supports a non-js and JS version of their site (A site that is interactive, not a blog or similar).