5 ms·
I'm not sure why so many HN posters feel the need to boast about not executing JavaScript. All that means is that you've opted out of the web that the rest of
by leftyted 8y ago
I'm not sure why so many HN posters feel the need to boast about not executing JavaScript.
All that means is that you've opted out of the web that the rest of the world is using. Good for you. But people who have disabled JS make up such a small porportion of web users (~.2% of pageviews) that your experience is pretty much irrelevant to the question of general browser trends.
I'd also bet that Chrome was faster at painting pages than Firefox, so it wasn't just a JS engine advantge.
- craftinator 8y agoI surmise it is because HN attracts a higher percentage of critical thinkers than many other boards. A startling amount of JS on the web falls into the following categories: 1) Advertisement 2) Tracking 3) Useless animation I don't care for any of those things. I generally prefer simple html pages that load <1 second, take very few resources, do not track any information about me, and don't use any mouse-reactive animations while I'm trying to get work done.
- peruvian 8y agoIt's more likely that most of the "critical thinkers" you speak of write JavaScript for money everyday. Even on HN the amount of JS blockers is tiny but it seems higher because they always have to mention they block JS.
- droidist2 8y agoSo is "I block JS" the new "I don't own a TV"?
- craftinator 8y agoI also don't own a TV. And as soon as I go vegan, I'll gain superpowers and ascend into the Mothership, where I can hang out with Tom Cruise and Ronny Hubbard!
- a1369209993 8y agoFWIW, I also don't use a TV[0]; I just don't bring it up often because it's rarely relevant. I brought up javascript because javascript is usualy the reason why <any webbrowser that executes javascript> is slower than <any webbrowser that doesn't executes javascript>. See "do less stuff". 0: unless you count monitors as TVs, or disassembly-for-parts as use.
- a1369209993 8y ago> I'd also bet that Chrome was faster at painting pages than Firefox, so it wasn't just a JS engine advantge. That may very well have been true, but if Chrome spends 10 cycles rendering the page and 100 cycles executing malware, and Firefox spends 20 cycles rendering the page and zero cycles executing malware, Chrome still loses despite being being twice as fast at the only thing that matters.