>Whether websites have to work without any JavaScript at all is a question almost as old as the web itself. By now, the answer is clear: No, they don’t. It’s firmly established that websites should be more than just structured and styled text. JavaScript execution is an integral part of (almost) every browser.
You‘re absolutely right, not every web page „should“ include interactive elements.
What I wanted to express is that web pages shouldn’t be forced into being only structured styled Text and instead should be encouraged to embrace interactivity.
The "refresh causes load" issue can be solved by doing long-polling instead of short-polling.
Note that the http-equiv refresh will only trigger after the page is fully-loaded, which long-polling does not allows to happen, so you do have resilience for the case where the long-poll is interrupted mysteriously.
I haven’t tried this yet, but if it works this would be a very smart solution to the problem, as it could potentially also reduce delays between turns.
The trend to CDNs serving static content means that Javascript becomes far more important than before, so "no-javascript" sites are at a huge disadvantage.
For instance, you can load up the same static page for everybody, then after it's loaded, serve some small personalized Javascript that refers to your particular user account which then customizes the page.
I realized this during my exercise: I had to completely disable pre-rendering in SvelteKit for the account system to work without JS, since I want to show the username for logged in users.
>Whether websites have to work without any JavaScript at all is a question almost as old as the web itself. By now, the answer is clear: No, they don’t. It’s firmly established that websites should be more than just structured and styled text. JavaScript execution is an integral part of (almost) every browser.
The page this text is on, proves that isn't true!
You‘re absolutely right, not every web page „should“ include interactive elements.
What I wanted to express is that web pages shouldn’t be forced into being only structured styled Text and instead should be encouraged to embrace interactivity.
The "refresh causes load" issue can be solved by doing long-polling instead of short-polling.
Note that the http-equiv refresh will only trigger after the page is fully-loaded, which long-polling does not allows to happen, so you do have resilience for the case where the long-poll is interrupted mysteriously.
I haven’t tried this yet, but if it works this would be a very smart solution to the problem, as it could potentially also reduce delays between turns.
The trend to CDNs serving static content means that Javascript becomes far more important than before, so "no-javascript" sites are at a huge disadvantage.
For instance, you can load up the same static page for everybody, then after it's loaded, serve some small personalized Javascript that refers to your particular user account which then customizes the page.
I realized this during my exercise: I had to completely disable pre-rendering in SvelteKit for the account system to work without JS, since I want to show the username for logged in users.