A lot of pages even fail if you only disable 3rd-party scripts.
I consider them broken, since the platform is to render a Document Object Model, scripting is secondary functionality and no fallbacks are bad practice. Imagine if that were a pdf/epub.
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.
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.
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.
Skill issue - on the devs side.
A lot of pages even fail if you only disable 3rd-party scripts.
I consider them broken, since the platform is to render a Document Object Model, scripting is secondary functionality and no fallbacks are bad practice. Imagine if that were a pdf/epub.
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.
*cost-efficient. At this point it’s a race to the bottom.
and its not even the devs. its the higher ups forcing them to do shit that won’t work.
Yep, burnout-rate increasing, companies favoring quantity over quality.
Devs are lazy but also product people and design request stuff that even modern CSS cannot do
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.
please never turn anything into an electron app
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.
More simple websites have some advantages like, less work to maintain, responsivity and accessibility by default.
Sure, what is already, that is. It starts already at choosing the frameworks.