Why I hate your Single Page App
medium.freecodecamp.org
Why I hate your Single Page App
1–10 of 128 posts
Re: Why I hate your Single Page App
#2This looks like it needs a (2016) tag in the title.
Re: Why I hate your Single Page App
#3Answer: "Maybe your single page app is different, but the ones that I know break most of my browser’s features, such as the back and forward buttons, page refresh, bookmarking, sending a link, or opening a link in a new window or tab."
Re: Why I hate your Single Page App
#4[deleted]
Re: Why I hate your Single Page App
#5None of the things described here are inherent to single page apps. Ember (with Ember Data and proper routing), for example, solves most of the issues he brings up (back button not working, failure to link to individual items) by convention.
Re: Why I hate your Single Page App
#6This. A thousand times this. And if you do it for a content site, you deserve a special place in hell.
Re: Why I hate your Single Page App
#7Answer: "Maybe your single page app is different, but the ones that I know break most of my browser’s features, such as the back and forward buttons, page refresh, bookmarking, sending a link, or opening a link in a new window or tab."
Yeah, these are problems. 2017 and the browser still doesn't know what the javascript is trying to accomplish
Re: Why I hate your Single Page App
#8I really hate articles that have a large fixed header at the top, that causes the next few lines of text to be hidden when I hit page down. Something something glass houses and throwing stones.
Re: Why I hate your Single Page App
#9I've always liked JQueryMobile because it breaks so few things. I haven't tried some of the newer alternatives.
Re: Why I hate your Single Page App
#10Web browsers were designed to deliver stateless documents to users.
Modern users want content delivered to them in a personal, rapid, contextual(stateful) manner
Fight.