Why is everyone so slow to move to http3?
HTTPX2 isn't about the protocol version, it's the name of a python library to make http requests.
But yes, it doesn't support HTTP3. Here's the related issue: https://github.com/pydantic/httpx2/issues/92
because its over QUIC, which is different enough to be a pain.
Not that there is anything wrong with QUIC, at least its built by someone who knows what they are doing, unlike HTTP2
that's not really much of an argument, almost all reasonable libraries wrap the functionality.and if a provider doesn't want to support http3 then the library will fallback, and then the laggards should pay the slow tax.
No as in the infra between you and the end user is less developed.
Nobody is going to get fired for using http1.1
if you move to http3 and a bunch of clients cant use your site, then you're gonna get yelled at.
Why would you assume that we have to move from techX to techX+1? If I release http4 would you assume that you have to migrate to http4 at some point?
HTTPX2 isn't about the protocol version, it's the name of a python library to make http requests.
But yes, it doesn't support HTTP3. Here's the related issue: https://github.com/pydantic/httpx2/issues/92
because its over QUIC, which is different enough to be a pain.
Not that there is anything wrong with QUIC, at least its built by someone who knows what they are doing, unlike HTTP2
that's not really much of an argument, almost all reasonable libraries wrap the functionality.and if a provider doesn't want to support http3 then the library will fallback, and then the laggards should pay the slow tax.
No as in the infra between you and the end user is less developed.
Nobody is going to get fired for using http1.1
if you move to http3 and a bunch of clients cant use your site, then you're gonna get yelled at.
Why would you assume that we have to move from techX to techX+1? If I release http4 would you assume that you have to migrate to http4 at some point?