3 ms·
NoScript gives you a 90s style web experience. It's vastly superior to what passes for normal these days and blows away AMP pages on page load performance.
by kevin_thibedeau 4y ago
NoScript gives you a 90s style web experience. It's vastly superior to what passes for normal these days and blows away AMP pages on page load performance.
- GoblinSlayer 4y agoAnd for the most egregious cases of broken design, which are sadly regular, you need to disable styling too.
- jakzurr 4y agoYup, many sites just read faster without the cruft. For me, everything has continued to get faster for the past 30 years. Better modems, service, dsl, cable. 15 years ago, installed button on browser at work to turn off scripting (all or nothing). Used until NoScript came out. Most news sites, NYTimes, WPost, CNN, even HN - you don't even need scripting to read the text, and it loads like lightning. I don't even bother with an add blocker these days. Want to see pics? Tweak the pic link yourself, or google the article title. Worth it, because it's so much faster. On HN, I finally got a log in and enabled scripting for ycombinator.com - it's usually always fast anyway. Example: to follow the war in Ukraine at https://www.scribblemaps.com/maps/view/The-War-in-Ukraine/091194 https://www.scribblemaps.com/maps/view/The-War-in-Ukraine/09... - I just enable "scribblemaps.com". Don't need "azure.com", "google-analytics.com", or "visualstudio.com". Most sites I leave default, no scripting at all. If I really want to see missing content, I might try enabling some, or even all, if I trust the site. Most of the time I can read everything I want without wasting the time.
- UI_at_80x24 4y agoI was a huge fan of NoScript when it first came out and depended on it extensively until FireFox changed something on their backend and it broke NoScript. Then NoScript released an updated version of the extension and honestly I had a terrible time trying to figure out how to use it. IIRC there was some kind of grid format used that was entirely opaque to me; yet the developer must have thought was an improvement over the previous "allow X.domain.com temporarily" vs "allow X.domain.com permanently." that I was used to. I should give it another try, maybe it's not as obscure as it once was. EDIT: I've just reinstalled it, and it is much more intuitive then it was before. Thank-you for reminded me about it.