(thread)
okay, no, actually, I think it's actively harmful when a page is intended to display static information - text and images you can't edit - and requires javascript to do it
any website building tool which functions that way is actively doing harm
no we will not explain
"no I will not explain" = "no I can't explain" but trying anyway re: javascript static sites
take as an assumption that resource expenditure matters
kay? let's start there
the bandwidth required to transmit fonts, text, images, and so on matters
the electricity spent on computation to execute scripts matters
the resources mined and burned to build machines capable of processing and presenting data matters
all of this matters
now imagine the exact opposite of that
building everything on top of a pile of client side javascript is what that exact opposite implies
"how much electricity is your website burning because you built it to run on scripts instead of being just text and images?", we ask.
they don't care, so they use these script website tools
"how much more electricity will be burned if the tools you give website builders make mountains of javascript?", we ask.
they don't care, so they build these script website tools.
and that doesn't even get into our next question: "why should we trust you to run code on our computers?", we ask.
they don't care about that either.
yes, we hate these things because they're rubbish
but we hate them more because they're born out of indifference and callousness at best, and active hostility at worst