Live data from Hacker News

A day without JavaScript

sonniesedge.co.uk

81–90 of 412 posts

Re: A day without JavaScript

#81

I generally agree with what he is saying, but the web has moved beyond the point where its reasonable to expect websites to have JS fallbacks. It is just too prominent now a days. I've always been a JS hater, though I have to code it frequently.. However, with that said I find the arguments against the language becoming more and more obsolete as the years go on.

> I generally agree with what he is saying

"I’m a 30-something woman living in Berlin, Germany (the famous one, with the wall and stuff)."

https://sonniesedge.co.uk/about/

Re: A day without JavaScript

#82
post #55

Earlier quoted context omitted.

Naw, I will keep running noscript and blocking script by default. If your site doesn't work, I don't care, I will go to a different one. I may be the minority now, and while there is some great use of js out there; most of it is bloated, slow, insecure, and often privacy destroying.

I honestly think the security/privacy arguments are the only valid argument against requiring JS as standard. The idea of browsers sending data that the user has explicitly elected to send (in addition to, if we're being pedantic, that the server put there in the first place) is very compelling in this day and age - only problem being that in order for that to have any meaningful impact on web security in the general…

What about power consumption as another valid argument? Your battery will last longer without Javascript.

Re: A day without JavaScript

#84
post #72
post #38

> For me it’s a matter of elegance and simplicity over unnecessary complexity. Simplicity is having one place where the DOM is created and managed, and optimizing for the 99% use case. Complexity is splitting up DOM rendering over two networked systems for servicing a 1% use case. Browsers are JS runtimes now. Get over it.

You're not vmg from Twitter, are you? This post is less reasonable than I would expect.

I'm not

Re: A day without JavaScript

#85
post #59
post #38

> For me it’s a matter of elegance and simplicity over unnecessary complexity. Simplicity is having one place where the DOM is created and managed, and optimizing for the 99% use case. Complexity is splitting up DOM rendering over two networked systems for servicing a 1% use case. Browsers are JS runtimes now. Get over it.

> Browsers are JS runtimes now. Get over it. Sure, dude, ignore anyone without a machine that can run MBs of JS within a reasonable time.

> Sure, dude, ignore anyone without a machine that can run MBs of JS within a reasonable time.

I'd wager 90% can even run the strawman you're building

Re: A day without JavaScript

#86

Having browsed nearly JS-free for the last two-ish years, aside from a bit of tweaking at the start, I have to say that it has made things a lot faster, more stable, and just much more of a pleasure to navigate. If anyone is interested, I have found that two tools make life a lot easier: - NoScript, which blocks execution of scripts save for those you whitelist. This means sites that reasonably require JS (e.g. YouTu…

NoScript doesn't actually work half the time; even when you whitelist a site through it the site could well remain busted. Source: bitter experience.

Re: A day without JavaScript

#87
post #82

Earlier quoted context omitted.

I honestly think the security/privacy arguments are the only valid argument against requiring JS as standard. The idea of browsers sending data that the user has explicitly elected to send (in addition to, if we're being pedantic, that the server put there in the first place) is very compelling in this day and age - only problem being that in order for that to have any meaningful impact on web security in the general…

What about power consumption as another valid argument? Your battery will last longer without Javascript.

It will last even longer without CSS

Re: A day without JavaScript

#88
post #70

Earlier quoted context omitted.

Also, vast majority of users will have a cached copy of jQuery from Google CDN already. Now bundling it with the rest of your JS, that's indeed a mistake.

CDNs are a lie. The privacy implications outweigh the performance benefits since there are many, many, many CDNs and many, many versions of jQuery. It's rare for users to benefit from caching.

I believe this is true, but the world will only be convinced if there are metrics for this. Are you aware of anything that verifies it?

Re: A day without JavaScript

#89
post #71

Earlier quoted context omitted.

That is fair, but when was the last time when a js only site was running on optimized JS?

All google products. But it is ridiculous to disregard JavaScript because some people can't write it properly. It is the same as saying that I wouldn't use a browser because I once went to a website that displayed a popup.

There is a massive difference in downloading tonnes of JS every other day because there's a new React bundle and between having annoyance _once_.

Re: A day without JavaScript

#90
post #59
post #38

> For me it’s a matter of elegance and simplicity over unnecessary complexity. Simplicity is having one place where the DOM is created and managed, and optimizing for the 99% use case. Complexity is splitting up DOM rendering over two networked systems for servicing a 1% use case. Browsers are JS runtimes now. Get over it.

> Browsers are JS runtimes now. Get over it. Sure, dude, ignore anyone without a machine that can run MBs of JS within a reasonable time.

Why are you trying to browse the modern Web on your Windows 98 potato from last century?
Post reply on HN