←back to thread

CRLF is obsolete and should be abolished

(fossil-scm.org)
422 points km | 2 comments | 13 Oct 24 19:16 UTC | HN request time: 0s | source
Show context
perching_aix ◴[13 Oct 24 20:09 UTC] No.41831129[source]▶
Well, at least the title is honest. Straight up asking people to break standards out of sheer conviction is a new one for me personally, but it's definitely one of the attitudes of all time, so maybe it's just me being green.

Can we ask for the typical *nix text editors to disobey the POSIX standard of a text file next, so that I don't need to use hex editing to get trailing newlines off the end of files?

replies(4): >>41831233 #>>41831275 #>>41831592 #>>41833146 #
bigstrat2003 ◴[13 Oct 24 21:07 UTC] No.41831592[source]▶
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).
replies(1): >>41831612 #
Ekaros ◴[13 Oct 24 21:09 UTC] No.41831612[source]▶
If 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.
replies(1): >>41831994 #
1. nsnshsuejeb ◴[13 Oct 24 21:51 UTC] No.41831994[source]▶
No need. Just convince the king (e.g. Google for HTTP) to make a tweak in the next standard version.
replies(1): >>41836672 #
2. vitus ◴[14 Oct 24 11:55 UTC] No.41836672[source]▶
Good 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.