News for hackers. Stuff that matters.

A comment on HTTP/3: the past, the present, and the future. Parent comment

Re:HTTP/3: the past, the present, and the future by _klm7 on Thursday September 26, 2019 @06:08PM (#21086107)
I have an idea: maybe software engineers and tech managers could take a bit longer to do things, so that they don't have to rush to fix them later. Because it's exactly what HTTP/3 sounds: a rushed fix for the HTTP/2 screw up.
[ Parent | on HN ]
Re:HTTP/3: the past, the present, and the future by zamadatix on Thursday September 26, 2019 @07:18PM (#21086699)
I think you should look into the histories of HTTP/2 and HTTP/3 before making such claims. These were both in development and deployment as proprietary protocols used by Google (in Chrome and other things) for nearly 10 years before being officially ratified.
[ Parent | on HN ]
Re:HTTP/3: the past, the present, and the future by dragonwriter on Thursday September 26, 2019 @07:12PM (#21086637)
> Because it's exactly what HTTP/3 sounds: a rushed fix for the HTTP/2 screw up.

Wasn't Google already publishing and promoting QUIC before SPDY got adopted as the basis for HTTP/2? SPDY was more conservative because it didn't replace TCP, QUIC wasn't a fix for SPDY being broken, it was a concurrent and less conservative effort poo.

[ Parent | on HN ]
Re:HTTP/3: the past, the present, and the future by dragonwriter on Thursday September 26, 2019 @10:44PM (#21087945)
Missed the edit window, I have no idea how “poo” got there.
[ Parent | on HN ]