No
No
The main beef I have with this site is that when I go to it with JS switched off, all I get is a message telling me to switch it on. There's no information about why I should switch it on - what will I get in return for switching it on, and what will the site take as a result of me switching it on. What am I missing by having JS switched off.
So, instead of the site just saying "JavaScript is required. Please enable it to continue." instead it should say something like "This web page contains an interactive game that requires JavaScript to function. Please enable it to continue." Then I know that there's actually something interesting being done with the JS, and not just a lazy webmaster who can't be bothered to display a blog post correctly.
Also for sites where JS is not required but is used to enhance interactivity a note to say that the difference is with/without JS would be useful ("without JS this site will work, but be slower due to more round-trips to the server" or "without JS this site will be less pretty") then you can choose if you care enough about the difference.
Not earth-shattering by any account, but not everything has to be.
As a side note: the question isn't relevant to the comment you replied to, your reply would have been better posted at top level where the people seeing it is not filtered by taking out those who have decided to skip the thread about JS complaint complaints.
I find it very debatable that putting information on the internet does not come with associated mandatory responsibilities
Having content that requires javascript? Eeehhhhhh. When static content like blog posts and news articles require JS it’s annoying. But for a little game like this the dev’s choice makes sense. Losing a few % of their audience is a reasonable trade in exchange for not needing to implement the whole thing twice. It’s really hard to get worked up about server side rendering for toys like this.
I suggest you pick your battles differently. This is a silly hill to die on.
Accessibility could be a valid concern, though many accessibility tools cope with common JS patterns so if your concern really is accessibility (rather than "jcelerier is entitled to have all content without running JS") then please show what you think the problem is there.
I mean, it could have been made as a server-side app, but going SPA makes sense here from a practical standpoint.
What's next, a bunch of complaining that electron apps are slow? That people are writing video games in managed languages?
It's just so frustrating to watch how having loads of Javascript on websites that absolutely don't need it has been normalized. I don't think people should be blamed for using Javascript (or Electron, .NET, whatever), especially for hobby projects. But I also think users shouldn't be silent about it, especially since there are young developers who actually don't know software could be better. It's just such a massive waste of resources and breaks accesibility way to often.
This is already implemented in any browser I know, but for some reason it is available only to some functionality (microphone, camera etc.) but not for eg. Ajax, Cross-Origin Things, Websockets, Canvas2D, WebGL etc.
Also before executing any Javascript browsers should ask if you want this website to execute (potentially malicious) code on your computer!
There are many documented browser-exploits and basically all newer ones that are actually a danger to users involve Javascript. It's also not reasonable to assume that people only visit trusted sites.