12 ms·
My main reason is because there is no support for it in Ruby yet, been waiting for a while. Usually I would try to release such a missing gem myself but HTTP/3
by Alifatisk 2y ago
My main reason is because there is no support for it in Ruby yet, been waiting for a while. Usually I would try to release such a missing gem myself but HTTP/3 is waaay to complex for me.
Also, I remember when asking for why there was no support for HTTP/3 yet in Rails, someone responded something along the lines of no true benefit of using H3 over H2. But I can't find that comment again.
- PikachuEXE 2y agoDo you mean server or client? On server side I think I handle it in reverse proxy and/or CDN. Client side I don't see anything HTTP/3 related yet.
- Alifatisk 2y agoServer