News for hackers. Stuff that matters.
Re:Stimulus: A modest JavaScript framework for the HTML you ... by jacobsenscott on Tuesday January 02, 2018 @11:08PM (#16058294)
I've used turbolinks in production and it is great. The progress bar is clunky, but it is optional, and not needed anyway if your pages render in a reasonable amount of time (100ms to 200ms is "instant" to most people). I can't really fathom how the parent to your post saw a slowdown using turbolinks - because the server doesn't know the difference, and the client does less work.
Re:Stimulus: A modest JavaScript framework for the HTML you ... by JoshMnem on Wednesday January 03, 2018 @02:04AM (#16059127)
Turbolinks is often a terrible user experience. The user doesn't measure page load in seconds, but in the perceived load in seconds. Turbolinks on slow connections feels painful, including on big sites with fast servers, like YouTube and Github.
Re:Stimulus: A modest JavaScript framework for the HTML you ... by ksec on Wednesday January 03, 2018 @06:45AM (#16060204)
Can you define what do you mean by slow connection?
Re:Stimulus: A modest JavaScript framework for the HTML you ... by JoshMnem on Wednesday January 03, 2018 @11:24AM (#16062281)
I often work at cafes. Sometimes the connections are slow. I sometimes middle-click the links open (new tab) to avoid having to wait for turbolinks.
Re:Stimulus: A modest JavaScript framework for the HTML you ... by titusjohnson on Wednesday January 03, 2018 @03:22PM (#16064690)
You know you'll wait the same amount of time, right?
Re:Stimulus: A modest JavaScript framework for the HTML you ... by JoshMnem on Sunday January 07, 2018 @06:02AM (#16090358)
My comment above mentions that. It's about perceived page load time. There are small tricks that sites do to make UIs appear faster, even if they aren't really faster. Turbolinks has the opposite effect, making the loading appear to be worse on bad connections or when there are other rendering problems.