Zitat

Basic content should be accessible to all web browsers
Basic functionality should be accessible to all web browsers
Sparse, semantic markup contains all content
Enhanced layout is provided by externally linked CSS
Enhanced behavior is provided by unobtrusive, externally linked JavaScript
End-user web browser preferences are respected

Zitat

I surf the web with NoScript (a FireFox extension to block java script on a per-domain basis, the sake of security). That also enforces "js; dr". Some pages show absolutely no content unless you allow JS from their domain, and perhaps others. I often don't bother; just back button out of there and go somewhere else.

Zitat

I am seeing more and more single-page apps that are nothing more than documents, blogs or articles for which relying on JavaScript is not appropriate. Often this breaks down one way or another (back button, stuck "loading" screen, bad formatting).

Zitat

js;dr = JavaScript required; Didn’t Read.
Pages that are empty without JS: dead to history (archive-org), unreliable for search results (despite any search engine claims of JS support, check it yourself), and thus ignorable. No need to waste time reading or responding.

Also known as, if it’s not curlable, it’s not on the web.

https://indiewebcamp.com/curlable

Because in 10 years nothing you built today that depends on JS for the content will be available, visible, or archived anywhere on the web.


All your fancy front-end-JS-required frameworks are dead to history, a mere evolutionary blip in web app development practices. Perhaps they provided interesting ephemeral prototypes, nothing more.

Zitat von »indexofrefraction«

@ tomasparks
well krpano itself is js, so it does not make much sense to avoid js completely :-D