4 ms·
Yes, you can. Maybe you even should, because then you at least understand all the moving parts. Because there are way too many shitty SPAs out there that break
by WA 9y ago
Yes, you can. Maybe you even should, because then you at least understand all the moving parts. Because there are way too many shitty SPAs out there that break functionality (Twitter and Facebook when hitting the back button) or are annoyingly slow and unreliable (iTunes Connect, Play Developer Console). Read [1] to see all the disadvantages and understand them. Then maybe build an SPA.
[1]: https://adamsilver.io/articles/the-disadvantages-of-single-page-applications/ https://adamsilver.io/articles/the-disadvantages-of-single-p...
- cname 9y agoBuilding your own is educational and maybe even fun (to a point), but it's not going to magically fix these kinds of issues. Most if not all frameworks support navigation and custom framework XYZ probably isn't going to do a better job. The fact that some sites do a bad job at navigation, performance, or whatever really seems orthogonal to me. We can also come up with numerous examples of "classic" sites that are slow, bloated, and have a bad UX.
- WA 9y agoThat’s precisely my point: a good SPA is more than a framework and the only thing that helps to make it good is education.