5 ms·

I think this article is overly negative, some of the cases are not _always_ a disadvantage. Take "fast back" as an example. If your app is interactive and upda

by augustl 11y ago

I think this article is overly negative, some of the cases are not _always_ a disadvantage. Take "fast back" as an example. If your app is interactive and updates live, the "back" page can already be up and running with the latest data, instead of first loading a cached version and then having it update with JS later. Also, personally I'm not so sure users care about things like the "stop" button working. And "fast back" depends on the situation. Having said that: if these kinds of articles reduce the risk of things like blogger.com being a SPA, keep writing :)

JustSomeNobody 11y ago
Why would users not care about the stop button working? If something in the browser is not loading, I want to hit stop so I can wait a while before trying again.
- nkassis 11y ago
  What would a stop button in Word be like? It really depends on the type of webapp and experience you are trying to create.
  - JustSomeNobody 11y ago
    Ah, but see, the stop button, back and forward, scrolling down, etc. are how the web worked. And best practice has always been, "don't break the web". Now... people break things. We went from having a consistent UI experience in the browser to everyone just making stuff up. Not good.
    - spoiler 11y ago
      I believe that some things shouldn't be SPAs (but, unfortunately are). Some of our clients[1] use SPAs for regular websites (which just makes me eyeroll). A good example for a SPA would be something like a webmail client, a word processor, or a chat. A bad example of it would be a blog, or a product website; these are much more suited for MPW I'm conflicted wheteher these would benefit from a SPA or not: discussion boards, web shops and the like. I can see them benefiting from SPA, but I can also see some disadvantages. I guess they'd be more suited for a "hybrid solution" (MPW with some AJAX and/or WebSockets). [1]: I work for a hosting company, so our clients are usually web developers (or sometimes they hire web developers).
    - augustl 11y ago
      If browsers had hooks for "the page has now finished loading" (to display a loading indicator while the page loads with XHR etc) and "callback for stop button click" I'm sure lots of SPAs would put them to good use :)
      - JustSomeNobody 11y ago
        So, it is the browser's fault. Nice.
        augustl 11y ago
        If we can agree that SPAs are useful for some type of apps, it's definitely the browsers lack of APIs fault that the SPA has no way of telling the browser about these sort of things, yeah.
  - qu4z-2 11y ago
    Word also doesn't generally lock up when it can't access the network, and sit there spinning though. (Although I'm sure that feature is on the road-map). I feel like a lot of the people making SPAs just haven't used a dodgy internet connection in five years or more.
    - jalfresi 11y ago
      I get the impression they are all too young to remember the dark old days of Flash web apps. We've been here before. It sucked.
      - JustSomeNobody 11y ago
        Indeed!
  - jalfresi 11y ago
    IT would probably be like the time when everyone used Flash to create web apps and reproduced the browser functionality like back and stop, confusing users and breaking the web. Rule #1 of the web: Don't break the web

by augustl 11y ago

JustSomeNobody 11y ago

Why would users not care about the stop button working? If something in the browser is not loading, I want to hit stop so I can wait a while before trying again.

nkassis 11y ago
What would a stop button in Word be like? It really depends on the type of webapp and experience you are trying to create.
- JustSomeNobody 11y ago
  Ah, but see, the stop button, back and forward, scrolling down, etc. are how the web worked. And best practice has always been, "don't break the web". Now... people break things. We went from having a consistent UI experience in the browser to everyone just making stuff up. Not good.
  - spoiler 11y ago
    I believe that some things shouldn't be SPAs (but, unfortunately are). Some of our clients[1] use SPAs for regular websites (which just makes me eyeroll). A good example for a SPA would be something like a webmail client, a word processor, or a chat. A bad example of it would be a blog, or a product website; these are much more suited for MPW I'm conflicted wheteher these would benefit from a SPA or not: discussion boards, web shops and the like. I can see them benefiting from SPA, but I can also see some disadvantages. I guess they'd be more suited for a "hybrid solution" (MPW with some AJAX and/or WebSockets). [1]: I work for a hosting company, so our clients are usually web developers (or sometimes they hire web developers).
  - augustl 11y ago
    If browsers had hooks for "the page has now finished loading" (to display a loading indicator while the page loads with XHR etc) and "callback for stop button click" I'm sure lots of SPAs would put them to good use :)
    - JustSomeNobody 11y ago
      So, it is the browser's fault. Nice.
      - augustl 11y ago
        If we can agree that SPAs are useful for some type of apps, it's definitely the browsers lack of APIs fault that the SPA has no way of telling the browser about these sort of things, yeah.
- qu4z-2 11y ago
  Word also doesn't generally lock up when it can't access the network, and sit there spinning though. (Although I'm sure that feature is on the road-map). I feel like a lot of the people making SPAs just haven't used a dodgy internet connection in five years or more.
  - jalfresi 11y ago
    I get the impression they are all too young to remember the dark old days of Flash web apps. We've been here before. It sucked.
    - JustSomeNobody 11y ago
      Indeed!
- jalfresi 11y ago
  IT would probably be like the time when everyone used Flash to create web apps and reproduced the browser functionality like back and stop, confusing users and breaking the web. Rule #1 of the web: Don't break the web