No. I didn’t take this site as a religious anti-Turing-tarpit sermon. Rather it is saying that not every load of your page will run the JS. 99% might but 1% wo

No. I didn’t take this site as a religious anti-Turing-tarpit sermon. Rather it is saying that not every load of your page will run the JS. 99% might but 1% won’t to make up some stats. So you need to decide how your app behaves when there is no JS. I work for a very rich desktop experience web app company where there is nothing you can do! Best things is have a nicely styled “sorry” message as a default. If you are operating a mail client, maybe you can have a seperate low fi mode. Or choose a tech that allows server side rendering, which is running that JS on the server and then losing up that page. There are trades offs for every site. From no-JS-in-the-first-place static marketing sites to web app versions of native apps with all the whistles. It comes back to technical and architectural and UX design. The post here is a reminder. Some of your client loads won’t have JS running, of that you can be sure.