News for hackers. Stuff that matters.
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.

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.

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.