3 ms·
The author of this piece seems to be glossing over something rather important: If you need to provide both a javascript-enabled and a no-javascript method of do
by eridius 15y ago
The author of this piece seems to be glossing over something rather important: If you need to provide both a javascript-enabled and a no-javascript method of doing the same work, then you're effectively writing duplicated code. Whether this is something you actually want to provide should depend on your target audience, and how much you really care about chasing after the folks who disable JavaScript or are otherwise unable to use the JavaScript-enabled solution. There are probably also accessibility concerns here (how compatible are JavaScript-heavy apps and screen readers?). But none of this means that you are a bad person if you write a web app that requires JavaScript to function.