3 ms·
Right, because all we ever need it is more complexity, no backwards compatibility, and more speed in all terms /s Come on. Networks are extremely FAST by now,
by pmlnr 6y ago
Right, because all we ever need it is more complexity, no backwards compatibility, and more speed in all terms /s
Come on. Networks are extremely FAST by now, TCP or not. It's the silly amount of JS computation pushed to the client that is slow, both in download speed and on the client.
- Spivak 6y agoBut we have backwards compatibility right now. That's, like, the whole point of the OSI model. Any device that supports UDP can handle QUIC with no fanfare like it was any other application-layer protocol because it is!
- pmlnr 6y agoWe have fallbacks, that's not the same as backwards compatibility. They call this HTTP3, and they shouldn't; it's not HTTP.
- Spivak 6y agoThat was the case with HTTP2 as well though. The client can negotiate with the server about supported protocols but if a client only spoke HTTP1.1 and the server only spoke HTTP2 they simply couldn't talk. It's just that basically no servers were HTTP2 only.