3 ms·
Lots of absolute views in this thread. How about: If it's profitable for your site to offer a non-JS fallback, do it. If it isn't, don't.
by mkilling 13y ago
Lots of absolute views in this thread.
How about: If it's profitable for your site to offer a non-JS fallback, do it. If it isn't, don't.
- drdaeman 13y agoThere are other things besides personal financial profits. Think of them as taxes to maintain Internet working and flexible. If you don't pay that tax, you're personally contributing to a future when simple documents become full-fledged programs, and everyone lose abilities to easily manipulate and interact with them in any but author-defined ways. There are cases where you can be exempt from that tax - if your site is not about documents, but their transformations, i.e. it's more of a process, not data. (Then you should call it app, not site). But vast majority of sites isn't.