no fallbacks is bad practice.

This is how you know they're extra lazy -- no "please enable javascript because we suck and have no noscript version".

wild thing is that with modern css and local fonts (nerdfonts, etc), you can make a simple page with a modern grid and nested css without requiring a single third party library or js.

devs are just lazy.

Personally, I love server-side rendering, I think it's the best way to ensure your content works the way YOU built it. However, offloading the processing to the client saves money, and makes sense if you're also planning on turning it into an electron app.

I feel it's better practice to use a DNS that blocks traffic for known telemetry and malware.

Personally, I used to blacklist all scripts and turn them on one at a time till I had the functionality I needed.

All modern browsers have Javascript enabled by default. A good dev targets and tests for mainstream systems.

But they're not pdf/e-pub, they're live pages that support changing things in the DOM dynamically. I'm sorry, I'm not trying to be mean but people not wanting scripting on their sites are a niche inside a niche, so in terms of prioritising fixing things that's a very small audience with a very small ROI if done they might require a huge rewrite. It's just not financially feasible for not much of a reason other than puritan ones.

I generally do the same. In fact, on desktop, uBO is set to hard mode. Unfortunately, I do need to access these sites from time to time.

Same. This is the way.

I'm a webdev. I agree. I like react.

because modern young/unskilled webdevs cant do anything without react

There are plenty of modern frameworks most of which as better. Even the lightweight ones need JavaScript.

It's like JavaScript is used way over its reasonable use cases and you need a thick layer of framework indirection to be able to do anything, and yet still sucks.