|
|
|
|
|
by hmwhy
1916 days ago
|
|
I set NoScript to disallow all JavaScript by default and whitelist those that I "trust" as I go, I have been doing that for a few years now. The friction in surfing doesn't get lower over time, not least because my exposure to most non-whitelisted websites are through websites like HN, but it's also not high enough that I would consider not blocking JavaScript by default. Websites that use a lot of third-party JavaScript are red flags to me; more often than not, they are unrelated to critical functionalities (such as payment), and they add absolutely no value to the client. Perhaps one thing that is worth noting is that modern frameworks that are SSG-focused or hybrids like Next.js make developing websites for JavaScript-blocking clients a bit easier. I haven't personally looked into this too closely, but at least with the website projects that I have work on with Next.js, you would still get a presentable bare-minimum with little effort when JavaScript is turned off, it's also not difficult to implement a reasonable fallback for JavaScript-blocking clients. The above of course depends on how much server data need to be fetched dynamically to render a page, which again depends on the nature of the content on a website. If I'm not mistaken, there are functionalities that simply can't be implemented, or very impractical to implement, without JavaScript; in those cases the question of "making it work for that 0.2%" is probably moot. |
|