3 ms·
It's one of those "live by the sword, die by the sword" issues as far as I'm concerned. At least with IE6, a lot of people are stuck with it due to locked-down
by ticks 14y ago
It's one of those "live by the sword, die by the sword" issues as far as I'm concerned. At least with IE6, a lot of people are stuck with it due to locked-down corporate networks; whereas with JS, people who are opting-out should blame themselves - unless I'm missing an obvious web browser that doesn't support it? That said, I too offer minimal support for non-JS'ers.
- dhume 14y agowith 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).
- Drbble 14y agoTry a multithreading browser, such as, all of them?