← Graph

Do you end up fighting Turbo when adopting these new APIs?

question 3 connections

Audience asks whether using Hotwire, prefetching, and Turbo broadcasts on models forces you to fight Turbo when applying Ryan's techniques. Answer: generally Turbo works fine — Rails aligns well with the web (HTTP caching, etc.) and Rails origins already lead on Core Web Vitals. Use measurement to find where the actual problem is; Turbo itself is usually not it. The exciting possibility is that the Declarative Partial Updates API could standardize what Turbo does for everyone, so front-end component libraries from outside the Rails ecosystem could start integrating with Rails backends naturally instead of Rails living in its own world. Dealing in HTML is faster than passing JSON and rendering on the client.

answer_summary
Turbo rarely fights these APIs; measure first. Declarative Partial Updates could standardize Turbo's model, letting Rails integrate with the broader frontend ecosystem.
question Do you end up fighting Turbo when adopting these new APIs?
about
Turbo tool
Question centers on Turbo + Turbo broadcasts interop.
question Do you end up fighting Turbo when adopting these new APIs?
about
Ryan's answer points to this API as a future standardization of Turbo's model.
question Do you end up fighting Turbo when adopting these new APIs?
asked_at
Asked during the Q&A.

Provenance

Read by
1 extraction