Re:State is hard: why SPAs will persist
by RHSeeger on Sunday May 29, 2022 @02:38PM
(#31551595)
My negative reaction to SPAs is as a user, not a developer. There are so many places where SPA behavior runs counter to my intuition as a user (breaking the back button being the single most glaring issue) that I just don't like them in general. Sure, all these places _can_ be fixed with enough code; but they shouldn't need to be. Unless the application is one that clearly benefits from being implemented as a SPA, it shouldn't be one.
[ Parent
| on HN ]
breaking "open in new tab" annoys me far more (and also seems to be way more common)
that and the fact that SPAs, not intrinsically, but often are so sluggish
Re:State is hard: why SPAs will persist
by friendlypeg on Monday May 30, 2022 @12:05AM
(#31555363)
You can see this broken behaviour in the revamped Play Store website. It makes you wonder whether no one at Google felt this was a problem or just didn't bother to fix it.
It also REALLY messes with custom URL redirection rules IME. Because it bypasses the page load, the rules just get ignored.
Re:State is hard: why SPAs will persist
by robertoandred on Sunday May 29, 2022 @02:39PM
(#31551603)
Breaking the back button is not SPA behavior.
It's a common behavior in SPA that's uncommon elsewhere. Kind of like how buffer overflows aren't C behavior.
Re:State is hard: why SPAs will persist
by andrewstuart2 on Sunday May 29, 2022 @08:45PM
(#31554390)
I've had at least as many WebApps I've used built with JSP or ASP et al that broke back via unrepeatable POSTs and server side state as I have with SPAs.
While I agree that the back button _should_ work in an SPA, it's common for it not to. And it's common for other functionality to break. It's not hard to fix that and, for a well engineered SPA, such things typically do work. However, it _is_ extra work and it _does_ get missed. As such, SPAs tend to have more issues than non-SPAs. As such, as a user, I tend to prefer non-SPA implementations unless there is a strong reason that the SPA makes more sense.
It’s very common in poorly engineered SPAs. “Built in” browser functionality often has to be reimplemented.
Bad developers are still not a valid argument against SPAs.
If it is more common for functionality to be broken in an SPA than in a non-SPA, then that most certainly _is_ a valid argument against SPAs (from a user perspective). It's not an argument that all SPAs are bad. Rather, that I prefer non-SPA implementations because I can generally assume that it will have fewer bugs/annoyances in using it.
Why not? "You have to reimplement a huge amount of current and future behaviors that just work for MPAs" is definitely an argument against SPAs. That's extra work, extra potential for bugs, extra potential for accessibility problems.
It sort-of is if bad developers are less likely to wreck havoc with MPAs. Also, I don’t think that back-button breakage automatically indicates incompetent developers (although I tend to swear at them).
That's like saying bad trapeze artists are not a valid argument for safety nets.
Re:State is hard: why SPAs will persist
by trivialsoup on Sunday May 29, 2022 @06:09PM
(#31553360)
Not only is it not implicitly SPA behavior, as you say, good back button behavior design is actually hard in a app setting. And you can’t generally “get it right” — no matter what you do, in a sufficiently complex scenario (which… that’s why you built an SPA, right?) users will disagree about what the back button should do!
Generalized anti-SPA sentiment is silly. Saying “bad implementations correspond with SPA” is true but also silly because there’s not as much to get wrong in non-app settings which admit a “traditional” approach. It’s like the xkcd observation about heat maps and population density.