SPA is mostly useful for reducing the cost of large application deployments. It improves speed for loading the initial bootstraping of the application. That means index is delivered almost instantly, and depending on the async loading of the code, can be dramatically speed up. SPA will reduce the overall server-rending of content besides json results which will be compressed, and json is smaller than html markup. Also SPA provides for a more sophisticated user experience. But like all things, the original cars got people from a-z, but not in style or comfort. As technologies improve over time, so will the reasons for using SPA. Browsers eventually will allow offline browsing as a standard feature, and having the SPA JS installed & json written to localstore/indexedDB will make using that UI rather nice, instead of always getting a 404 response when you have no internet and such. SPA is about control, server-rendered requires connectivity and difficulty handling response when failure occurs. 1st Major SPA's were email clients, consider google's gmail or microsoft web outlook service for exchange servers. Huge benefit with SPA, because the UI is complex and should not be constantly refreshing, because it can cause contextual change on what is displayed and present in-app state from re-initialization.
How we switched our template rendering engine to React
41–42 of 42 posts
Re: How we switched our template rendering engine to React
#42Earlier quoted context omitted.
Downvoted for positivity, damn HN. That's harsh.
From the hn guidelines: "Please resist commenting about being downvoted. It never does any good, and it makes boring reading."
Well it was that or just assume that HN comments are only for bitching about minor discrepancies in the article, nerdy holy wars, or for general negativity.
Of course that's the general impression outside HN so perhaps they're correct and I'm just fighting a lost cause.