You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We use Turbolinks to emulate a single-page application, which was the default Rails configuration for years.
However, Turbolinks is no longer being developed, and its last release took place in 2018. It has been replaced by Turbo.
On the other hand, Turbolinks adds complexity to our application in many ways, and we expect Turbo to behave similarly. It also provides a different user experience than most pages since it doesn't use the browser's default mechanism showing that a page is being loaded, which might confuse some people. What would happen if we removed it? Would we have a performance penalty?
Definition of Done
A prototype (i.e. not everything needs to work) replacing Turbolinks with Turbo is provided
A prototype removing Turbolinks is provided (you can find one in a commit in the remove_tubolinks branch)
A performance comparison between using Turbo and removing Turbolinks is provided
The text was updated successfully, but these errors were encountered:
Background
We use Turbolinks to emulate a single-page application, which was the default Rails configuration for years.
However, Turbolinks is no longer being developed, and its last release took place in 2018. It has been replaced by Turbo.
On the other hand, Turbolinks adds complexity to our application in many ways, and we expect Turbo to behave similarly. It also provides a different user experience than most pages since it doesn't use the browser's default mechanism showing that a page is being loaded, which might confuse some people. What would happen if we removed it? Would we have a performance penalty?
Definition of Done
The text was updated successfully, but these errors were encountered: