3 ms·
Yeah, I have no idea what the author is smoking. Deliberately breaking standards is simply not an acceptable solution to the problem, even if it were a serious
by bigstrat2003 2y ago
Yeah, I have no idea what the author is smoking. Deliberately breaking standards is simply not an acceptable solution to the problem, even if it were a serious problem (it's not).
- Ekaros 2y agoIf there truly is a problem with existing protocols, propose and properly design new one that can replace it. Then if it is technically superior solution it should win in long run.
- nsnshsuejeb 2y agoNo need. Just convince the king (e.g. Google for HTTP) to make a tweak in the next standard version.
- vitus 2y agoGood news! Both HTTP/2 and HTTP/3 use a packed binary representation for headers, so CRLF is nowhere to be found in RFC 9113 / 9114. I don't see value in picking on Google or HTTP here, even if it is fashionable to do so.