Live data from Hacker News

I Turned Off JavaScript for a Week

wired.com

71–80 of 93 posts

Re: I Turned Off JavaScript for a Week

#71
post #50

> and I could browse the web with fewer distractions—all without the sense of guilt that comes with using an ad blocker Never felt the slightest skerrick of guilt for using an ad blocker. Instead I feel mildly virtuous in doing my own small part in helping the idea of an ad-supported internet die.

If not ads what do you want? Paywalls? Native content? Personally I want a robust and diverse web ecosystem, not just pay walls and people forced to alternative revenue sources.

Re: I Turned Off JavaScript for a Week

#72

Earlier quoted context omitted.

Keep in mind Google is blocked in China, so if you include jQuery from Google, it's not going to work for over a billion people.

Is it really fair to include the total population of China in this statement?

Yes, it's fair, because many developers live in a little bubble. The United States, Canada, Australia, Russia and all of Europe combined is only 15% of the world's population.

You can argue the other 85% doesn't have internet access or isn't your target audience. However, I run a site that's geared to the US market, it's entirely in English, and 12k of my registered users are from China (1.5%). If I included files from the Google CDN, I'd be losing 1.5% of my users due to one line of code.

Re: I Turned Off JavaScript for a Week

#73
post #60

Whoa, this guy managed to uncheck "enable javascript" somehow? Glad to read such a cutting edge article. In seriousness, disabling javascript (and enabling it selectively when things inevitably break when I was using NoScript) grew too tedious for me after a while. There are simply too many sites that require JS to function properly. Others may disagree and enjoy clicking constantly to enable select javascripts to ge…

> In seriousness, disabling javascript (and enabling it selectively when things inevitably break when I was using NoScript) grew too tedious for me after a while. I'm sort of inclined to agree. I really want to like NoScript, but every now and then when I use NoScript for a couple of weeks I get frustrated with it and disable it. Sure, having it disabled is also frustrating, but it's a different kind of frustration a…

I guess I have less diverse browsing habits than you guys. I use noscript very happily. I whitelisted what I need for sites that I use years ago and most things I do now "just work" (most is ~95% the other things I temporarily allow). When e.g. a job application needs a javascript heavy online test I open up another profile with no addons and use that profile for that that thing. Based on experiences using browsers without noscript I think that the "faff time" (for me) from doing what I do is less than the "waiting for excessive javascript" and "figuring out that this site has overriden scrolling/back button".

Re: I Turned Off JavaScript for a Week

#74
post #28
post #19

Earlier quoted context omitted.

I think that simple content such as blogs, news and the equivalent should not be implemented in js-dependent web apps. Web browsers are a platform for sure, but the simple content should stay simple.

It have thought for a while now that the web and correspondingly the browser should be bifurcated into a content platform with no client side code and an application platform without the burden of the older technologies. The browser would provide all the interactivity and logic for the content platform through implementations of standard html tags. For the application platform, the browser could provide a more conven…

I can't agree more. I was just saying something similar in the thread on mobile JS framework loading performance. The browser has reached a critical stage where the Jekyll/Hide impersonation has got to stop. There needs to be separate modes in the browser, application/content, or there needs to be separate browsers. The evolution of JS as a decorative language has reached its ultimate end: it's no longer just decorative and instead is now devouring and devaluing the host content it was supposed to originally enhance. But, at the same time, it's usefulness for zero-install client-side applications cannot be ignored and it needs a platform also.

Re: I Turned Off JavaScript for a Week

#75

Sure. If you believe that the browser should only be a document reader and not an application platform then go ahead. It's kinda like buying a smartphone and then using it exclusively as a phone though.... I think the real point of irritation here is all the 3rd party junk that gets loaded in that has nothing to do with the main functionality of the site that you are on.

I believe the browser should be exactly what it is, without using javascript. I'll always block javascript, whitelisting sites which 1) fail to work without it and 2) which i really want to visit. If you need javascript to present information then you're either not a very good developer or else you don't care about the user experience. Degrade gracefully; you can still display text and images without javascript and a…

That's fine, but there is still a place for JS-only applications on the web. For example, we produce a web application development IDE that emits JS-only applications (HTML just bootstraps the JS). The things you can do with such applications are numerous, and are the backbone of a lot of SAAS offerings. However, our company web site doesn't use any JS (other than the Google Analytics hook), and it loads/runs like a dream on any device/browser. The point here is that there is a rationale for both modes of operation (content vs. application), and maybe, like another commenter noted here, it's just time to bite the bullet and separate out the two use cases in a more forceful and clear manner.

Re: I Turned Off JavaScript for a Week

#76
In Firefox, the "disable javascript" checkbox is now gone from the settings --why would they do that?

But it can still be disabled in `about:config` > `javascript.enabled`

I used and loved Firefox since more than 10 years so far, but can't truly understand some decisions they took.

Re: I Turned Off JavaScript for a Week

#77
I've been doing this for a while now after becoming tuned into the tracking and particularly fingerprinting being done. The web is surprisingly usable with it off. I use SafeScript in Chrome which generally works ok. I use multiple profiles in Chrome, one with just Adblock the other with Adblock, noscript, httpseverywhere, privacy badger, etc. I use the normal one where I absolutely must and that doesn't keep cookies.

I'm not paranoid and I don't have anything to hide but I object to being tracked to have stuff sold to me.

Re: I Turned Off JavaScript for a Week

#78
post #76

In Firefox, the "disable javascript" checkbox is now gone from the settings --why would they do that? But it can still be disabled in `about:config` > `javascript.enabled` I used and loved Firefox since more than 10 years so far, but can't truly understand some decisions they took.

I read about this a while back if I remember correctly it's because people kept turning it off accidentally and breaking the Internet and blaming Firefox.

Re: I Turned Off JavaScript for a Week

#79
post #76

In Firefox, the "disable javascript" checkbox is now gone from the settings --why would they do that? But it can still be disabled in `about:config` > `javascript.enabled` I used and loved Firefox since more than 10 years so far, but can't truly understand some decisions they took.

Just download NoScript - it's better than turning JavaScript off and on all the time anyway.

Re: I Turned Off JavaScript for a Week

#80
post #65

Earlier quoted context omitted.

You only save bandwidth the first time the resource is accessed. After that it's loaded from the browser cache! So over time, the band-witch saving by minification is insignificant.

So, the answer to bojo's question is "Yes.". > After that it's loaded from the browser cache! Unless the resource changes, the UA's cache is cleared, the file is served with incorrect caching headers, the cache expiry time specified in the resource header is reached, the resource is loaded by a UA that doesn't cache...

Lets say your .js files takes up 5% of your total app size after gzip compression, and minification saves you around 20%. Then you have saved around 1% bandwidth at the cost of obfuscation and more difficult debugging. And If it's cached, witch all main-steam browsers does, you've saved around 0.01% at best. So if you pay $10,000 in bandwidth costs each month, that's $1 saved :P
Post reply on HN