4 ms·
Long ago Ruby on rails had a feature that sort of cached all links on the current page to make navigating to them faster. What happened to that? Would that not
by darau1 6y ago
Long ago Ruby on rails had a feature that sort of cached all links on the current page to make navigating to them faster. What happened to that? Would that not provide the same speed benefit? I'm ignoring the inefficient use of data here, ofc.
- nitrogen 6y agoIt's still a thing: https://turbo.hotwire.dev/ https://turbo.hotwire.dev/ HTML fragments are not all that less efficient than JSON on the wire, and they are much more CPU efficient for low-powered client devices.
- mrinterweb 6y agoI think you're referring to TurboLinks. TurboLinks is still around. Building on that technology and moving towards HTML over socket is https://hotwire.dev/ https://hotwire.dev/
- drspacemonkey 6y agoThat would be TurboLinks. It's going strong, and has seen significant improvements over time. Especially when paired with something like Stimulus and/or Reflex and/or Hotwire, you can make some _very_ snappy feeling server-side rendered HTML. At this point, I won't even consider making SPAs for anything unless the product owner has an incredibly compelling reason. If you're curious what the modern state of server-side HTML Rails can be from the user's perspective, head over to hey.com and sign up for their free trial.