News for hackers. Stuff that matters.

A comment on Turbolinks: SPA-like Experience without the SPA-framework Hassle. Parent comment

Re:Turbolinks: SPA-like Experience without the SPA-framework... by the_gastropod on Monday December 11, 2017 @01:47PM (#15899239)
Turbolinks is not a front-end framework. It is a library that has been in Rails for ~5 years. And before that, pjax did basically the same exact thing. This is a pretty battle-tested way of building web applications.
[ Parent | on HN ]
Re:Turbolinks: SPA-like Experience without the SPA-framework... by deckar01 on Monday December 11, 2017 @11:27PM (#15903000)
GitLab removed TurboLinks from their site not that long ago. It was the source of a lot of bugs, crufty code, and flakey tests. If you have any JavaScript that modifies the DOM or ever plan to don’t use TurboLinks.
[ Parent | on HN ]
Re:Turbolinks: SPA-like Experience without the SPA-framework... by pbreit on Tuesday December 12, 2017 @02:16AM (#15903619)
Shopify went back to Turbolinks: https://shopifyengineering.myshopify.com/blogs/engineering/r...
[ Parent | on HN ]
Re:Turbolinks: SPA-like Experience without the SPA-framework... by deckar01 on Tuesday December 12, 2017 @11:32AM (#15906860)
That article is from 2014, the golden age of TurboLinks. As far as I can tell they are not using it on their main site or any of their white labeled sites anymore.

https://github.com/shopify-graveyard/turbolinks/

[ Parent | on HN ]
Re:Turbolinks: SPA-like Experience without the SPA-framework... by Rafert on Tuesday December 12, 2017 @12:59PM (#15907802)
They forked: https://github.com/Shopify/turbograft to add partial page replacements. It was slated to be merged in TurboLinks 3 but that canned in favour of version 5.

Their new Polaris components are using React though: https://github.com/shopify/polaris

[ Parent | on HN ]
Re:Turbolinks: SPA-like Experience without the SPA-framework... by owens99 on Tuesday December 12, 2017 @11:06AM (#15906583)
> GitLab removed TurboLinks from their site not that long ago. It was the source of a lot of bugs, crufty code, and flakey tests.

An anecdote is not data.

[ Parent | on HN ]
Re:Turbolinks: SPA-like Experience without the SPA-framework... by deckar01 on Tuesday December 12, 2017 @11:36AM (#15906893)
> Turbolinks.clearCache() Removes all entries from the Turbolinks page cache. Call this when state has changed on the server that may affect cached pages.

https://github.com/turbolinks/turbolinks#turbolinksclearcach...

This is a nightmare. You will eventually miss a cache invalidation and break browser navigation or invalidate the cache so aggressively that TurboLinks is serving no purpose.

You don't need lots of negative testimonials to see that managing your own client side cache with JavaScript is a bad idea.

[ Parent | on HN ]
Re:Turbolinks: SPA-like Experience without the SPA-framework... by owens99 on Wednesday December 13, 2017 @05:54PM (#15918477)
Haven't had any problems with this in 2 years in production. It also works fine for Basecamp.
[ Parent | on HN ]