2 ms·
1) The applications you develop/design (I infer) have a very limited kind of interaction, or have no need to support offline conditions and/or real-time data. T
by yuchi 8y ago
1) The applications you develop/design (I infer) have a very limited kind of interaction, or have no need to support offline conditions and/or real-time data. This is not the case for the rest of the world.
2) what you propose is completely different from the proposal in the link. I’d be ok with a JS-off-by-default world (or a cookie-off-by-default too!!) but having a limit on file size is just… miopic.
- irq11 8y agoYou’re right on the second point: I think it’s somewhat silly to set an arbitrary size limit (an easy javascript off button would be fantastic, however.) Your first point misses the argument. It’s not that you should support everything with JS disabled; you should, however, support a subset of your interaction as a fallback. Yeah, users don’t get offline mode or whizzy ajax updates, but you can absolutely find a way to work, in nearly all apps. And it isn’t that hard. The fact that so many people believe this is impossible is an indication of how low the front-end development bar has fallen. This is why we have webpages that take 10MB of JS to render 300k of text.