News for hackers. Stuff that matters.
Re:JavaScript Disabled: Should I Care? by eric_bullington on Sunday September 21, 2014 @12:38PM (#8347524)
I think it's critical here to distinguish between full client-side application (e.g., gmail) and an informational web site (e.g., a news site, a blog, or code documentation). It's a bad idea to require Javascript for the latter, but it's equally silly to try to build a fully-responsive client application using no Javascript, or progressive enhancement.

In several of my recent sites, there's been a main company site requiring no Javascript, but then a portal to one or more applications or services that requires Javascript.

In these cases, Javascript is taking the place of what before might have been Java applets, Flash apps, or Silverlight applications. But it's arguably more secure, fairly standardized, and "installed" by default.

And in the cases of full browser applications, I think it's silly to argue against requiring Javascript. You simply can't build a fully responsive client-side application using just HTTP calls and static HTML, no matter how performant the server side.

And I will absolutely continue to use <noscript> tags for browser apps that run on Javascript, since it's rather rude to just show a white screen with no indication of what the problem is to users.

Re:JavaScript Disabled: Should I Care? by dllthomas on Sunday September 21, 2014 @12:55PM (#8347580)
I mostly agree, but would add that there seems to be a tendency to try and build a "full client-side application" out of things that needn't be one, which I think is a subtly different mistake than the one you were describing - which I would describe as "building a regular website as if it were a full client-side application".
Re:JavaScript Disabled: Should I Care? by themartorana on Sunday September 21, 2014 @01:18PM (#8347660)
But isn't that just artificially limiting yourself for no real reason? The no-JavaScript argument seems like IE6 repeating itself - intentionally dumbing down the capabilities at hand for a select few - except in this case (vs IE 6 in the aughts) it really is significantly "the few."

It might seem technically silly for me to have tons of parallax scrolling and DOM manipulation on my blog, but who cares?

I agree that decisions like this have the capacity to disrupt business in certain cases, but I don't see it being something that important in most businesses.

Edit: I'm taking a strong view here for certain, but I wonder who, outside an audience this technically literate, actually disables JS? True, the CDN argument is a good one, but in that case I assume most of my other static assets would be blocked as well.

Re:JavaScript Disabled: Should I Care? by agwa on Sunday September 21, 2014 @01:59PM (#8347775)
Sites with minimal or no JavaScript are faster than sites with lots of JavaScript. The volume of JS is often so large, especially with frameworks, that it can take a long time both to transfer and to execute. I've noticed the difference to be significant on older computers or slower Internet connections, but it's even perceptible on new systems with fast Internet connections. Studies repeatedly show that ordinary users care about the speed of websites. I think this is a very good reason to shy away from making a "full client-side application" unless the benefits from that approach are significant.
Re:JavaScript Disabled: Should I Care? by seanp2k2 on Sunday September 21, 2014 @02:28PM (#8347861)
> Sites with minimal or no javascript are faster than sites with lots of javascript.

Though experiment: Simple todo app. Would this be faster if, upon every interaction with the UI, the whole form was sent to the server to recalculate a new DOM to send back to the browser to download + re-render? It certainly seems like e.g. adding a row to a DataTable would be what most users would call "faster".

Also, consider how this app scales. Requiring that the server re-build a page for every user interaction is a lot more work for the server vs. sending a big blob of HTML + assets once (CDNJS and similar services also affect how this performs). Given how powerful even a low-end few-year-old smartphone in the US is these days, I doubt that it would be a better experience to make an app like todo rely on server-side processing.

I do agree that javascript isn't /always/ the right tool, but building a few smaller API back-end + JS app front-end things lately been pretty convincing for me that JS + AJAX + REST API is a better UX for lots of things vs submit-and-rebuild. Clicking a radio button or selecting something in a drop-down and having the page refresh as a result feels pretty lame in 2014.

EDIT: note that I was a pretty dedicated NoScript user for a few years, a few years ago. These days, Privoxy running a few AB+ lists filters out almost all of the junk that annoys me (I found the performance of AB+ to be unacceptable with dozens of tabs open at once).

Re:JavaScript Disabled: Should I Care? by dllthomas on Sunday September 21, 2014 @02:35PM (#8347879)
"Clicking a radio button or selecting something in a drop-down and having the page refresh as a result feels pretty lame in 2014."

I find that's somewhat true until I'm sharing my todo list with others. Knowing that the rendered page represents a synchronous snapshot in time can be valuable, and is something that's often lost when moving to AJAX (though I certainly agree it doesn't have to be). Your point generally certainly holds - updates should be faster on a well-designed app, and ideally your JS will be cached.

Re:JavaScript Disabled: Should I Care? by agwa on Sunday September 21, 2014 @02:46PM (#8347911)
I think a TODO app would be an instance where the benefits of a "full client-side application" may be significant enough to outweigh the downsides, for the good reasons you describe.

I was a bit imprecise in the portion of my comment that you quoted; it was mainly a response to the parent's assertion that there was no reason to hold back from using JavaScript, even on his/her blog.

Re:JavaScript Disabled: Should I Care? by Benjamin_Dobell on Sunday September 21, 2014 @02:21PM (#8347841)
Studies don't show that users care about the speed of websites - they show that users care about the ease, and therefore "perceived speed", by which they can achieve a goal.

A website with a quality interactive UX that adapts to user's needs, ideally with minimal interruption, is going to be substantially more efficient for the user.

This is especially true since the very nature of web requires communicating with remote servers in order to update and persist the user's state. Loading an entire webpage every time state changes is not just slower, it's also quite disruptive for the user.

Javascript's power comes down to the fact it offers AJAX and a way to manipulate the DOM on the fly. In addition to avoiding full-page reloads, it has the advantage that you can present the user with meaningful UI i.e. progress indicators and what-not.

Re:JavaScript Disabled: Should I Care? by DanBC on Sunday September 21, 2014 @02:25PM (#8347858)
> A website with a quality interactive UX that adapts to user's needs, ideally with minimal interruption, is going to be substantially more efficient for the user.

That is a miniscule number of websites though.

Re:JavaScript Disabled: Should I Care? by Benjamin_Dobell on Sunday September 21, 2014 @02:37PM (#8347887)
If that's the case, then the problem isn't JS, it's poor web development. Annoying? Absolutely!

However, this is not a problem that users can expect to resolve on their end by doing something so general as disabling Javascript.

I could disable images, or ignore CSS, and undoubtedly websites would load faster for me also. However, complaining to the web-page maintainer that the webpage functions poorly on my system would hardly make sense.

Javascript is not the problem; I can make equally terrible UX for websites with-out it - small fonts, animated GIFs, terrible (any) audio... crap content.

If users want to complain and be taken seriously then they should complain about the problem, not something orthogonal to the issue.

Re:JavaScript Disabled: Should I Care? by dllthomas on Sunday September 21, 2014 @02:14PM (#8347815)
It's not just "the few" that browse with javascript disabled, though. It's also about making sure you play nice with assistive technology, that your content is visible to search engines, that you haven't broken URLs and browser history...

With HTML5, it's possible to do all this in a single page app. But it's a lot of work that you might not do or might get wrong, that you get for free when you treat web pages like web pages.

Re:JavaScript Disabled: Should I Care? by DanBC on Sunday September 21, 2014 @02:22PM (#8347843)
Certainly you're free to have huge globs of Javascript and CSS, but very many people have slow limited Internet connections and you're making life a (teeny tiny) bit worse for those people.

The important part of your blog is probably the text. We have hundreds of years of design iteration in the presentation of text and it's just weird to ignore all that.

Re:JavaScript Disabled: Should I Care? by scrollaway on Sunday September 21, 2014 @12:48PM (#8347552)
I'd like people to start more readily differenciating between web apps and documents (dynamic or not). I think we're at the point where it's obvious that there is a difference between the two and it's just as obvious requiring JS for web apps is completely acceptable.
Re:JavaScript Disabled: Should I Care? by dllthomas on Sunday September 21, 2014 @12:58PM (#8347593)
I think you are getting at an important distinction, but you're confused about what it actually is. The important question is, "What is the goal of this site? What is the best way to still meet that goal without JS?"

For documents, the answer is probably "provide the information", and that can trivially be accomplished without JS.

For some excruciatingly dynamic web apps, the answer might be "use someone else's product" or even "it can't be done".

There is substantial middle ground, though.

Re:JavaScript Disabled: Should I Care? by scrollaway on Sunday September 21, 2014 @01:06PM (#8347619)
So look at the middle-ground in terms of functionality, then. If a feature cannot be provided without JS, then don't provide it to those who don't have JS and move on. If the feature is not critical to other parts of the app, don't make those other parts depend on it.

This always seems to be a controversial discussion yet all it is about is a few well-understood rules:

- Manage your dependencies

- Don't break things on purpose because you don't like the user's setup

- Don't feel obligated to fully support platforms you have no desire of supporting

Re:JavaScript Disabled: Should I Care? by jiggy2011 on Sunday September 21, 2014 @02:39PM (#8347892)
The problem is keeping your code DRY when you have a mixture of two languages and execution environments. Inevitably you will have to choose which frameworks you want to use , picking two heavyweight frameworks for client and server will inevitably mean that they fight for control of your application if you want to use both to the fullest because each provides their own router and templating etc. So you need to decide which is going to drive your application.
Re:JavaScript Disabled: Should I Care? by eric_bullington on Sunday September 21, 2014 @03:02PM (#8347936)
>heavyweight frameworks for client and server will inevitably mean that they fight for control of your application

This is completely true, and I've found things to go best if I do one of two things:

1) Do a server side (template driven) app, using a server framework like Flask, ExpressJS, or else just Golang, with very light Javascript on the client, maybe using JQuery and Bootstrap for Javascript or else just pure Javascript. Minimal progressive enhancement.

2) Do a client-side app using a client framework like AngularJS or Backbone, or ReactJS, and build out a RESTful backend on the server side (or use Firebase or Parse.com). I even do authentication logic on the client now, since it's possible to do so securely. Not possible to use without Javascript.

In between these two extremes is a no man's land, particularly if you use big client and server frameworks (as you say pointed out). In my experience, such an approach can make it extremely difficult to build a coherent app structure.

Re:JavaScript Disabled: Should I Care? by dllthomas on Sunday September 21, 2014 @01:12PM (#8347637)
Well, treat each feature the same way, really. Offering a less comfortable but still functional experience is precisely what "progressive enhancement" is about. I agree that for many projects, at some point, there is functionality that can't be reasonably made accessible without JS, given the constraints of the project. I do think that many people seem to be too quick to go there. I don't think we have any major disagreement.
Re:JavaScript Disabled: Should I Care? by pdkl95 on Sunday September 21, 2014 @02:41PM (#8347896)
> it's rather rude to just show a white screen

Exactly.

In the case of something like gmail, while many of the features cannot [practically] be implemented without Javascript, it is always important to have some fallback. Even a dumb, read-only, paginated-<ul> of your inbox is useful.

I could be on a strange browser, or behind a restrictive or badly implemented firewall. Even just a message saying what should have been on the page can serve as a reason to come back when a proper browser is available.

Put another way: given the noscript extension exists, you should probably give at least <i>some</i> reason for people to click the whitelist button.

Just have something there; the Meteor style of not caring and sending an empty <body> tag just makes your site look like a broken webserver.

Re:JavaScript Disabled: Should I Care? by MrMember on Tuesday September 23, 2014 @10:32AM (#8355500)
Nothing frustrates me more than opening a link to a news article or some other text-based medium, seeing all of the text render normally, and then getting redirected to a page telling me to enable Javascript.