News for hackers. Stuff that matters.

A comment on Backbone.js 0.5.0 Released (with pushState). Parent comment

Re:Backbone.js 0.5.0 Released (with pushState) by jashkenas on Friday July 01, 2011 @02:44PM (#2719619)
Sure -- it depends where you draw the line for "acceptable", and how much you care about the experience of your IE users. In any single-page web app of significant size, I'd argue that it's never acceptable to do a full page refresh. Would you really want to go back to a GMail that refreshed when you clicked around between labels?

Regarding (2): hash-based URLs also work perfectly well for older browsers.

[ Parent | on HN ]
Re:Backbone.js 0.5.0 Released (with pushState) by catshirt on Friday July 01, 2011 @02:53PM (#2719656)
you're right, "acceptable" is subjective. but it doesn't seem unreasonable that if you are using an outdated version of a program, it will not perform optimally. to that end, managing both pushState and hashchange adds overhead and complexity. personally, i don't think enhancing old browsers is worth said overhead.

that said, if it was part of a framework i was using anyway, overhead and complexity are much less of an issue, so the question becomes "why not".

[ Parent | on HN ]