Re:Turbolinks: SPA-like Experience without the SPA-framework...
by pier25 on Monday December 11, 2017 @12:46PM
(#15898694)
The title is misleading since this is basically a TuboLinks article and doesn't really explore the problems of building an SPA without a framework.
[ Parent
| on HN ]
Re:Turbolinks: SPA-like Experience without the SPA-framework...
by sctb on Monday December 11, 2017 @02:05PM
(#15899382)
Thanks, we've updated it to a representative phrase from the article. We can change it again if someone suggests a better one.
Re:Turbolinks: SPA-like Experience without the SPA-framework...
by lailsonbm on Monday December 11, 2017 @04:38PM
(#15900715)
The title of the post was changed. @sctb (or any other moderator), can you please update it in this thread?
Re:Turbolinks: SPA-like Experience without the SPA-framework...
by sctb on Monday December 11, 2017 @05:47PM
(#15901401)
Sure thing, done.
Re:Turbolinks: SPA-like Experience without the SPA-framework...
by chickenfries on Monday December 11, 2017 @01:43PM
(#15899219)
Awful title. Guess no one would read it if it was called "how to use turbolinks."
Re:Turbolinks: SPA-like Experience without the SPA-framework...
by bodyloss on Monday December 11, 2017 @01:15PM
(#15898966)
Agreed. TurboLinks itself seems unnecessarily heavy. So you avoid a full page reload, but you do still have to fetch the whole page over the network and render it. Just without the browser loading icon spinning.
Re:Turbolinks: SPA-like Experience without the SPA-framework...
by ch4s3 on Monday December 11, 2017 @01:56PM
(#15899313)
Well, you can use data-turbolinks-permanent to prevent turbolinks from trashing a dom subtree, so that lightens it up a bit. Its also often paired with caching so that big chunks of the page are pulled from the cache so you can often do a sub 300ms refresh of the page with turbolinks while working well on slow mobile connections that choke on large js bundles.
It is complex in its own way though, so there's no free lunch here.