The idea behind turbolinks is good in general - it works great when you have a standard Rails application with its view stack (ERB). When I saw this talked, I liked it very much:
https://www.youtube.com/watch?v=SWEts0rlezA Unfortunately, we are not good fit. This works for a clean app which ERB and maybe little javascript. Foreman (and Katello) is a heavy JS app with various JS frameworks and perhaps it does not work well. At least this is my impression, I am very far from being a frontend developer :-) LZ On Wed, Dec 6, 2017 at 4:10 PM, Walden Raines <wrai...@redhat.com> wrote: > I am seeing more and more issues [1][2] around turbolinks and I'm wondering > if it's time to remove it from foreman. I have seen it recommended that one > shouldn't use the back button in foreman; I thought that request was > reserved for poorly written php sites that resubmit forms when the back > button is pressed, we're better than that! :) > > Are the benefits of turbolinks worth the cost? Does anyone have any metrics > on the difference in page load times with and without "turbo"links? > > Any additional thoughts on its removal? > > Cheers, > Walden > > [1] https://bugzilla.redhat.com/show_bug.cgi?id=1522740 > [2] http://projects.theforeman.org/issues/21480 > > -- > You received this message because you are subscribed to the Google Groups > "foreman-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to foreman-dev+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- Later, Lukas @lzap Zapletal -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
