Hacker News new | ask | show | jobs
by dhume 5176 days ago
with JS, people who are opting-out should blame themselves

No, I'm going to continue to blame that subset of JS coders who consume far too much of my CPU/memory resources. Thanks to them, I got to watch my browser slow to a crawl and become so unresponsive that it was difficult to even close the tab containing the offending site. The simplest solution is to have JS off by default. A whitelist system is nice for non-offending sites (I've never had this sort of trouble with JS on, say, HN).

1 comments

Try a multithreading browser, such as, all of them?