Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Everyone has JavaScript, right?

kryogenix.org

Post reply on HN
Print view View original

1–10 of 101 posts

Re: Everyone has JavaScript, right?

#3

Post by jmkni »

If CDN's based in the US need to do maintenance, they will probably do it late at night in the US, which might be at peak time for you if your website is based outside of the US.

Just a though.

Re: Everyone has JavaScript, right?

#4

Post by gtirloni »

I didn't get the point this website is trying to make. All distributed apps are like that at time of delivering the code. If that's so wrong with Javascript, what's the proposed alternative (that has a chance of being available everywhere)?

Re: Everyone has JavaScript, right?

#6

Post by cabirum »

Right, but these problems are not specific to javascript requests. Any request can fail, be blocked, interfered with, or partially received. Users can switch off CSS, too. Html page may not load completely. So what?

Some of these issues are fixed with https or http/2. Some with CDN fallbacks or just sane coding. Some are not developers problems - such as clueless users installing malicious extensions or luddite users switching off js.

Why not ask 'Everyone has html, right?'.

Re: Everyone has JavaScript, right?

#8

Post by dagingaa »

jmkni wrote: post #3

If CDN's based in the US need to do maintenance, they will probably do it late at night in the US , which might be at peak time for you if your website is based outside of the US. Just a though.

You might want to consider a different CDN in that case.

Re: Everyone has JavaScript, right?

#9

Post by moron4hire »

I'm not sure I entirely agree that JavaScript should be developed in a Progressive Enhancement style, for two reasons:

If you can live without it (the "progressive" part of progressive enhancement implies that the site is still usable without the JS), then I don't think you should be using JS at all. Semantic HTML and CSS are pretty amazing at adapting content fluidly and dynamically to a wide range of users and devices. Search engines expect documents to be laid out in a certain way. Web scrapers can add a whole pile of usefulness even to sites that don't create explicit public data APIs. You're going to have a serious hell of a time making it any better, and can easily make it a lot worse.

And on the other hand, content sites aren't the be-all, end-all of the Web anymore. The Web is increasingly a deployment platform for applications, and there are a whole host of applications that just can't be done in the browser without JS. Luddites who complain about "but I got JS disabled" aren't the target market for an image-editor-in-the-browser. Failing to load JS at that point is just plain failure to load the application and no amount of Progresso Soup is going to help you.

So yeah, I much prefer all or nothing.

Re: Everyone has JavaScript, right?

#10

Post by joelanman »

cabirum wrote: post #6

Right, but these problems are not specific to javascript requests. Any request can fail, be blocked, interfered with, or partially received. Users can switch off CSS, too. Html page may not load completely. So what? Some of these issues are fixed with https or http/2. Some with CDN fallbacks or just sane coding. Some are not developers problems - such as clueless users installing malicious extensions or luddite users…

The point being made is at the bottom - progressive enhancement. If at least the html makes it across the wire, a progressively enhanced website will still "work": you can still read content, click links, submit forms

http://jakearchibald.com/2013/progressive-enhancement-still-...

Post reply on HN