3 ms·
> 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.
by owens99 9y ago
> 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.
- deckar01 9y ago> 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#turbolinksclearcache 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.
- owens99 9y agoHaven't had any problems with this in 2 years in production. It also works fine for Basecamp.