Gregory's Server|
7 comments
 @mitsunee @vegafjord @nasser most of the shit JS gets is due to it being enabled by default. just imagine a web that grew up with adblockers in every browser, and opt-in for cookies and JSโฆ  @sofia there wouldn't be a reason to block JS if it wasn't for advertisers and other such nonsense @mitsunee i disagree. just because i visit your website does not mean i wanna run whatever code you have there. i think this would be a good disincentive to use JS for no good reason, which is like 95% of those websites that start of blank before you enable js. a static-ass website, but they gotta use some framework shit. @sofia if you don't wanna run my code then don't visit the site? My sites aren't blank without JS either, that problem got solved literally years ago and was merely caused by people overusing ui libraries without a framework that let's them work at scale. In fact it was never a problem for any of *my* sites. Fuck off with your pointless accusations. @mitsunee i really didn't mean to accuse you in particulat of making shitty websites, sorry if that's how it came across. it was meant to be a generic "you". the blank website phenomenon is very much still a thing, and it's super annoying, and yeah, framework fans promised me that would go away years agoโฆ running arbitrary code just seems like something that should have special permissions in a system that is stilll primarily used for documents. just like, say, camera access. @mitsunee i guess my feelinmg about frameworks are party motivated by me trying to and failing to understand React (i guess it has something to do with automatically synchronizing data and UI ๐คท). and when the main notable effect of this arcane magic is breaking static websites then that's just a bitโฆ disappointingโฆ |
@vegafjord fair enough, I just really dislike JS getting blamed for everything that's wrong with the web, even tho what's at fault are 80% advertisers and 20% "people" who don't understand users at all. I have a massively underoptimized blog that loads super quickly despite uselessly hydrating the entire text content on the page. It's never JS's fault.