2 ms·
> using a slower protocol because you can't be bothered to implement the latest standard. I thought we were discussing HTTP/2 but now you seem to be invoking H
by tuukkah 2y ago
> using a slower protocol because you can't be bothered to implement the latest standard.
I thought we were discussing HTTP/2 but now you seem to be invoking HTTP/3? It's even faster indeed but brings a whole lot of baggage with it. Nice comparison point though: Do you want to add the complexity of HTTP/2 or HTTP/3 in your backend? (I don't.)
- lmm 2y ago> I thought we were discussing HTTP/2 but now you seem to be invoking HTTP/3? The article talks about HTTP/2 but I suspect they're applying the same logic to HTTP/3. > Do you want to add the complexity of HTTP/2 or HTTP/3 in your backend? (I don't.) I'd like to use the same protocol all the way through. I wouldn't want to implement any HTTP standard by hand (I could, but I wouldn't for a normal application), but I'd expect an established language to have a solid library implementation available.