CRLF is obsolete and should be abolished

Re:CRLF is obsolete and should be abolished by Ekaros on Sunday October 13, 2024 @04:23PM (#41831256)

Thinking about it. Using CR alone in protocols actually make infinitely more sense. As that would allow use of LF in records. Which would make many use cases much simpler.

Just think about text protocols like HTTP, how much easier something like cookies would be to parse if you had CR as terminating character. And then each record separated by LF.

[ Parent | on HN ]

Re:CRLF is obsolete and should be abolished by mattmerr on Sunday October 13, 2024 @04:37PM (#41831369)

ASCII already has designated bytes for unit, group, and record separators. That aside, a big drawback of using unprintable bytes like these is they're more difficult for humans to read in dumps or type on a keyboard than a newline (provided newline has a strict definition CRLF, LF, etc)

[ Parent | on HN ]

Re:CRLF is obsolete and should be abolished by fijiaarone on Sunday October 13, 2024 @10:32PM (#41833693)

There is no reason those ascii characters need to stay unprintable. You could use other characters like an interpunct, silcrow, or down carat.

[ Parent | on HN ]

Re:CRLF is obsolete and should be abolished by eqvinox on Monday October 14, 2024 @04:31AM (#41835469)

There is in fact a reason those ASCII 'characters' should stay unprintable: the 0x00-0x1f (except Tab, CR, LF) range is explicitly excluded as invalid in a whole bunch of standards, e.g. XML.

[ Parent | on HN ]

Re:CRLF is obsolete and should be abolished by gpvos on Sunday October 13, 2024 @04:27PM (#41831290)

That is so backwards incompatible that it is never, ever going to fly.

[ Parent | on HN ]