3 ms·
I know they are comparing to HTTP2, but objectively HTTP2 was never a great fit for mobile. I know its not the case, but when HTTP2 was being developed it felt
by KaiserPro 5y ago
I know they are comparing to HTTP2, but objectively HTTP2 was never a great fit for mobile.
I know its not the case, but when HTTP2 was being developed it felt like they were only thinking about users with strong wifi and zero packet loss. My company had a number of reps at the W3C, whenever I raised concerns with them I was told that I was being an old sysadmin, and that tcp doesn't work the way I think it does. They were convinced that multiplexing down a single TCP pipe was better than having a pool of connections.
They were also convinced that the average size of webpages wasn't going to grow, despite lots of evidence to the contrary.
I'm still not entirely convinced that quic is the way forward either. However I haven't spent enough time looking at it to form a proper opinion.
- AgentME 5y agoQUIC has the solution to the issue you brought up with HTTP2: packet loss no longer causes all of the multiplexed streams to be interrupted, but without the costs of using many simultaneous TCP connections.