3 ms·
I thought http/2 was great for reducing latency for JS libraries like Turbo Links and Hotwire. Which is why the Rails crowd want it. Is that not the case?
by jonwinstanley 2y ago
I thought http/2 was great for reducing latency for JS libraries like Turbo Links and Hotwire.
Which is why the Rails crowd want it.
Is that not the case?
- the_duke 2y agoH2 still suffers from head of line blocking on unstable connections (like mobile). H3 is supposed to solve that.
- wtarreau 2y agoYep. Actually H1/H2/H3 do have the same problem (remember the good old days when everyone was trying to pipeline over H1?), except that H1 generally comes with multiple connections and H3 currently goes over QUIC and it's QUIC that addresses HoL by letting streams progress independently.