2 ms·
He makes a defense of the SPA that boils down to “because it’s easier to manage client side interactions that way.” The kicking point for server side is that t
by brightball 8y ago
He makes a defense of the SPA that boils down to “because it’s easier to manage client side interactions that way.”
The kicking point for server side is that the need for client side interaction is overblown. If you are building a tool that people will keep open for hours, by all means...SPA your heart out.
If you are building an open-check-close experience like most of the web, SPAs created more problems than they solve.
- bunderbunder 8y agoI'm thinking here of GitHub. GitHub's UI is not suffering for not being an SPA. On the contrary, it's improved by not being an SPA. When I'm browsing a repository, I cmd-click new tabs out all the time, and I also copy/paste links to individual files as of specific commits to coworkers fairly regularly. All of that kind of stuff is very useful UI that you basically get for free with a decent multi-page app. It gets a lot trickier to get right with an SPA. (I'm not actually sure I've ever seen someone pull it off.)