3 ms·
I'm very skeptical about QUIC/"HTTP3". TCP works extremely well already. Yes, one can do kind of better for some particular workloads but I have yet to see a su
by garganzol 6y ago
I'm very skeptical about QUIC/"HTTP3". TCP works extremely well already. Yes, one can do kind of better for some particular workloads but I have yet to see a successful implementation that goes ahead of TCP.
Take a Remote Desktop protocol used in Microsoft Windows. It can work over TCP but recent revisions tend to automatically switch to UDP. And know what? They are not reliable to the point that customers have to turn the UDP layer off. TCP gives a slightly worse latency but it is much more reliable and thus usable. Thanks there is a Group Policy for that.
I'm not even talking about Google as a company who constantly tries to attack the network infrastructure with its variant of EEE (Embrace, Extend and Extinguish). What's the end game? The crippled protocols worldwide imposed by the ad casino company? No, thank you. Internet must remain free of all of that.
- floatboth 6y ago> They are not reliable to the point that customers have to turn the UDP layer off I guess they didn't implement reliability then. This has nothing to do with QUIC. > Embrace, Extend and Extinguish Yeah, working on an IETF standard is EEE now? LOL
- garganzol 6y agoEEE 2.0. The social aspect is just an antitrust indulgence. Seems to be working fine for hoi polloi. For now, at least.