Re:Single Page Application Is Not a Silver Bullet
by thinkloop on Sunday February 04, 2018 @02:01PM
(#16304210)
The problem is even content is becoming functional with interactive charts, infographics and figures, videos, media, filtering, sorting - then the site will eventually need comments, ads, subscribing, favoriting, upvoting, login, lazy load next article, infinite scroll, etc. Yes, a pure content site shouldn't be an spa, but how long can you survive running a pure content site? Information is complex and the web allows us to communicate it more richly than the static 2d representations of old.
[ Parent
| on HN ]
Re:Single Page Application Is Not a Silver Bullet
by debaserab2 on Sunday February 04, 2018 @02:14PM
(#16304278)
What are static 2d representations?
You can do everything you mentioned without an spa just fine. Plenty of content sites (the majority, actually) survive just fine.
Re:Single Page Application Is Not a Silver Bullet
by nojvek on Sunday February 04, 2018 @09:38PM
(#16306247)
Well heβs taking about a hybrid. Each of your pages are essentially little applications on their own.
Re:Single Page Application Is Not a Silver Bullet
by fiatjaf on Sunday February 04, 2018 @07:58PM
(#16305876)
My solution is to use an isomorphic static-site SPA hybrid, as generated by https://github.com/fiatjaf/sitio, for example.
The idea is to load only the React components and the data needed for each route at load time. An example of a page generated with this technique: http://inflacao.org/series/
Re:Single Page Application Is Not a Silver Bullet
by same_shit on Sunday February 04, 2018 @11:17PM
(#16306564)
The problem is, this can all be solved with just a little bit of javascript to make interactive charts, infographics and figures, videos, media, filtering, sorting - then you can still serve static comments, ads, subscribing, favoriting, upvoting, login.