3 ms·
You'd simply need to know what those protocols are and how TCP works to understand the argument. Funnily enough most engineers don't seem to have any idea how
by mgaunard 4y ago
You'd simply need to know what those protocols are and how TCP works to understand the argument.
Funnily enough most engineers don't seem to have any idea how TCP works these days.
- ilyt 4y agoThat is an example of argument: > HTTP/2 is bad because XYZ, HTTP 3 at least fixes Z Note giving reasons, and preferably also reasoning behind those reasons. You know, the "arguments" Here is what clown riding that dunning-kruger peak thinks that "argument" is: > HTTP/2 is just plain silly, HTTP/3 is a silly idea but implemented correctly.
- mort96 4y agoYou provided no argument, there is nothing to understand.