Re:The Cost of JavaScript
by bo1024 on Wednesday November 15, 2017 @04:06PM
(#15707789)
I definitely admit it's a simplification that won't fit every scenario. It just turns out to be pretty apt for my web experience personally.
Maybe another way to put it is that I don't mind enabling and loading JS for a site where interactivity is clearly core functionality, but if it's essentially serving text, then a JS-heavy design feels like it's working against the user, not for the user.
Maybe another way to put it is that I don't mind enabling and loading JS for a site where interactivity is clearly core functionality, but if it's essentially serving text, then a JS-heavy design feels like it's working against the user, not for the user.