Live data from Hacker News

Ask HN: Why don't websites have 'text only' backup versions?

news.ycombinator.com

51–60 of 63 posts

Re: Ask HN: Why don't websites have 'text only' backup versions?

#51

The "proper" approach to this is 'progressive enhancement', ie. that every site is already a text only version. Then, on top of that, you can add images, stylesheets, Javascript, etc. as necessary. This used to work well, since that was also the easiest approach to building a site (unless you used Flash...) I think frameworks have inverted things: the easiest approach these days is to load the default config of some…

What CMS do you develop? This sounds like something I would use.

I always browse with cookies and Javascript disabled. There are very few sites I'll enable one or both to use. Most of the time, the first time I browse a site that requires Javascript to show anything useful I just leave. If you can't make your pitch with text, I'm pretty sure I'm not going to be interested.

I know, I know...I'm not the typical market for those kinds of sites.

Re: Ask HN: Why don't websites have 'text only' backup versions?

#52

The "proper" approach to this is 'progressive enhancement', ie. that every site is already a text only version. Then, on top of that, you can add images, stylesheets, Javascript, etc. as necessary. This used to work well, since that was also the easiest approach to building a site (unless you used Flash...) I think frameworks have inverted things: the easiest approach these days is to load the default config of some…

What CMS do you develop? This sounds like something I would use. I always browse with cookies and Javascript disabled. There are very few sites I'll enable one or both to use. Most of the time, the first time I browse a site that requires Javascript to show anything useful I just leave. If you can't make your pitch with text, I'm pretty sure I'm not going to be interested. I know, I know...I'm not the typical market…

I was a developer of http://ocportal.com a few years ago. I can't take much credit for it though, since my contribution was a drop in the ocean compared to that of Chris Graham.

Re: Ask HN: Why don't websites have 'text only' backup versions?

#53

Earlier quoted context omitted.

What CMS do you develop? This sounds like something I would use. I always browse with cookies and Javascript disabled. There are very few sites I'll enable one or both to use. Most of the time, the first time I browse a site that requires Javascript to show anything useful I just leave. If you can't make your pitch with text, I'm pretty sure I'm not going to be interested. I know, I know...I'm not the typical market…

I was a developer of http://ocportal.com a few years ago. I can't take much credit for it though, since my contribution was a drop in the ocean compared to that of Chris Graham.

Well done. Seems to work reasonably well without JS, which is more than far too many websites can say.

Well, except for the SWF animation at the top, and the dropdown menus, but meh.

Re: Ask HN: Why don't websites have 'text only' backup versions?

#55
post #45

That's not the way to help people with low bandwith or very high latency connections. They need more javascript, not less. SPA designs can actually make CRUD apps significantly more useable on slow or unreliable connections.

[Citation needed]

I've run across far too many "mobile-friendly" websites that start by loading many MBs of JS libraries. And just flat-out fail to load if any of said libraries fail to load.

Re: Ask HN: Why don't websites have 'text only' backup versions?

#56

When are we going to get over the idea of turning off javascript? No one asks "why doesn't my Java app run properly when I turn off the JVM?" I would argue that the open web is getting to that point with javascript. JS is an open standard, highly performant, and implemented well by almost every single browser out there. The only people I know who regularly browse without JS are old-timers who got into the habit 10 ye…

Running through:

W.r.t. "old-timers who got into the habit 10 years ago". A decade ago I was 11. Not exactly an old-timer.

W.r.t. performance, in an ideal world, you'd be absolutely right. But this is not an ideal world. There are far too many websites that are substantially less performant with JS. (Case in point: Gmail.). There are far too many websites that kill my battery life on my laptop via sloppy coding. There are far too many websites that don't stop downloading in the background to refresh things that I don't need refreshed, and in the process kill my bandwidth cap on my home connection. There are far too many websites that take multiple seconds before they even begin to render, because they are waiting on some library to load before they parse things clientside. Looking at you, client-side markdown. There are far too many websites that are less responsive on the "responsive" version with JS than with the fallback without JS.

W.r.t. download size, again, in an ideal world, you'd be absolutely right. But this is, again, not an ideal world. There are far too many websites that pull down multiple MB of libraries before they even start to load. Sometimes they are cached, but far too often they aren't. There are far too many websites, again, that refresh things that I don't need refreshed and as such continue to use bandwidth.

And you're missing two other things: the two concerns that I consider most important. One is security. The majority of browser exploits require JS, especially the nastier ones. As you say, JS engines focus heavily on performance. And trying to get high performance out of a JITted language goes intrinsically against security. For a certain amount of dev time, you can get decent security and decent performance, great performance and weak security, or great security and weak performance. It's an intrinsic trade-off. (The other one is user tracking, but I'm not going to get into that one here.)

And one other thing: with JS disabled, most of the time if a webpage is loaded it's actually loaded. I can keep it up and sit in a bus or something and read it, without an internet connection. With JS enabled, far too many websites end up breaking nastily some time down the line when they go to update something and fail. Again: not an intrinsic, but something far too many websites do anyways.

Re: Ask HN: Why don't websites have 'text only' backup versions?

#58
post #44
post #8

Because it isn't worth it, basically. It's a relatively simple economic decision - making a text only backup version takes time, programming, adds an extra possibility for failure, etc. etc. - and the people who want a text only version are an extremely small minority. I know that sounds a little heartless and "not caring about the web", but it's the reality.

It depends on the site, but it's really not that much effort for any site that a viewer would WANT a text-only mode. Sites with lots of text content invariably use a CMS to manage that content. It's not hard to build a text-only template, and in fact many sites actually do this - if you browse on mobile Safari, it's called "Reader Mode". I don't know if Android has an equivalent, but I would assume so.

I think you've acquired a mistaken picture of Reader Mode. Reader Mode (like the Readable and Readability bookmarklets) presents an alternative rendering of the same set of files from which the standard view is rendered: it does not cause the server to serve an alternative set of files.

Reader Mode and the Readable and Readability bookmarklets fail often even on "text-centric" pages such as blog posts.

Re: Ask HN: Why don't websites have 'text only' backup versions?

#59
post #4

I think main reason is that number of users with JS disabled these days is just too small to care. Another thing is even if the effort of enabling is small, people responsible for the website are not even aware of the problem. As an experiment I would drop a note to a few websites broken with JS disabled about a problem, providing a reasoning why it should be fixed and check how many respond.

I agree. The only people who disable JS are informed, and who wants those kinds of people visiting their website?! Ha! Good riddance, I say!

Re: Ask HN: Why don't websites have 'text only' backup versions?

#60
It basically amounts to two alternatives:

1) they make it intentional for whatever purpose - stop scrappers, prevent search engine indexing, pull in ads etc.

2) they make it out of incompetence - probably somebody with insufficient web development skills just used some popular JavaScript framework to quickly cook up a site

Now the majority of the customers won't care, but if you're targeting a professional audience, this will not score you any points. If you were a software development company hiring and I were to reply to your invitation, I would first go to your website. If I saw a blank screen in my browser, my first question to you would be why a serious company does have a broken site. Depending on what I heard I might skip you altogether.

Personally, I don't think there are any difficulties in doing a "text-only" version as you call it. That's how I always approach things - do a classic version then add some gradual enhancements. I can't imagine doing it the other way around actually.

And yes, you can call me out of touch with the times, but text pages rank higher and more credible in my eyes then all of the JavaScript toys I see around.

Post reply on HN