Odd, the article conclusion seems to directly contradict the title.
I've used both approaches over the years and they both seemed to work pretty well. The only differentiator I really noticed was that the single-page-app style (client) seemed to be more elegant on mobile, while the server rendering was easier to split into tabs on desktop browser.
I'm really a tab fanatic so have disliked the last few years of javascript everything on the client, where middle click stops working. Are there any solutions for that, that I've missed?
Links that represent navigation within the web app should still have a `href` attribute - even if click events are being handled with AJAX and pushState. That way middle-click, etc. work as expected.
Of course, some links don't actually represent navigation, so for them this isn't really applicable (e.g. a button to collapse an accordion-style view).
Comments
Odd, the article conclusion seems to directly contradict the title.
I've used both approaches over the years and they both seemed to work pretty well. The only differentiator I really noticed was that the single-page-app style (client) seemed to be more elegant on mobile, while the server rendering was easier to split into tabs on desktop browser.
I'm really a tab fanatic so have disliked the last few years of javascript everything on the client, where middle click stops working. Are there any solutions for that, that I've missed?
Links that represent navigation within the web app should still have a `href` attribute - even if click events are being handled with AJAX and pushState. That way middle-click, etc. work as expected.
Of course, some links don't actually represent navigation, so for them this isn't really applicable (e.g. a button to collapse an accordion-style view).