4 ms·

You would be right if 3G didn't jump down to 2G randomly, 4G does not have this flaw, 5G is meaningless. HTTP/1.1 is the final transport for humanity, but you

by bullen 5y ago

You would be right if 3G didn't jump down to 2G randomly, 4G does not have this flaw, 5G is meaningless. HTTP/1.1 is the final transport for humanity, but you need fiber (external IP, preferably static, but operators/governements are not helping) to sell something. HTTP/2 has head of line blocking issue. HTTP/3 wont become a standard outside of biased actors like Google.

rapsey 5y ago
Http3 works or will work soon in major browsers and cdn's. It will cary a large chunk of internet traffic.
chrismorgan 5y ago
A lot of the world has killed off 2G (e.g. in Australia it all got shut down 3–5 years ago), and it’s on the chopping block in a lot of the rest of the world (e.g. looks like the remaining 2G services in the USA goes EOL by the end of next year). 3G is also already on the chopping block in many places (e.g. looks like next year in the USA, and in Australia its spectrum has steadily been being reallocated in recent years, and the biggest telco is scheduled to kill it altogether in 2024). Fortunately after that it’s designed in compatible ways, so 4G and 5G and whatever comes after that can all coexist. For the HTTP versions, I’d put it more this way: HTTP/1.1 is the baseline that will continue to work forever. HTTP/2 is normally a significant improvement over HTTP/1.1, but it has one crucial flaw which makes it worse than the alternative of half a dozen HTTP/1.1 connections on connections with high packet loss. HTTP/3 is the best of both worlds, roundly better than HTTP/1 and HTTP/2, but because it’s using UDP, it’ll have some teething issues for a few years because of badly-configured corporate equipment. But it will become widely supported in server software—there’s no reason for it not to.
- bullen 5y ago
  I think most reasons for sequels is that people need something to do, HTTP/1.1 works for everything but people needs to feel they can improve things. Unfortunately everything peaks because of physics and energy. I'm not adding HTTP/2 or 3 to my HTTP app. server; HTTP/1.1 does everything I'll ever need and I have to focus on other things!
  - 411111111111111 5y ago
    You're probably not serving millions of users every day though. Btw, most production setups don't really have to do anything to support it, as pretty much all load balancers already do. And there isn't any big performance gain if it's only intranet traffic.

by bullen 5y ago

rapsey 5y ago

Http3 works or will work soon in major browsers and cdn's. It will cary a large chunk of internet traffic.

chrismorgan 5y ago

A lot of the world has killed off 2G (e.g. in Australia it all got shut down 3–5 years ago), and it’s on the chopping block in a lot of the rest of the world (e.g. looks like the remaining 2G services in the USA goes EOL by the end of next year). 3G is also already on the chopping block in many places (e.g. looks like next year in the USA, and in Australia its spectrum has steadily been being reallocated in recent years, and the biggest telco is scheduled to kill it altogether in 2024). Fortunately after that it’s designed in compatible ways, so 4G and 5G and whatever comes after that can all coexist. For the HTTP versions, I’d put it more this way: HTTP/1.1 is the baseline that will continue to work forever. HTTP/2 is normally a significant improvement over HTTP/1.1, but it has one crucial flaw which makes it worse than the alternative of half a dozen HTTP/1.1 connections on connections with high packet loss. HTTP/3 is the best of both worlds, roundly better than HTTP/1 and HTTP/2, but because it’s using UDP, it’ll have some teething issues for a few years because of badly-configured corporate equipment. But it will become widely supported in server software—there’s no reason for it not to.

bullen 5y ago
I think most reasons for sequels is that people need something to do, HTTP/1.1 works for everything but people needs to feel they can improve things. Unfortunately everything peaks because of physics and energy. I'm not adding HTTP/2 or 3 to my HTTP app. server; HTTP/1.1 does everything I'll ever need and I have to focus on other things!
- 411111111111111 5y ago
  You're probably not serving millions of users every day though. Btw, most production setups don't really have to do anything to support it, as pretty much all load balancers already do. And there isn't any big performance gain if it's only intranet traffic.