The author makes this assertion: > CR by itself is occasionally useful for when you want to overwrite a line of text you have just written. LF, on the other ha

The author makes this assertion: > CR by itself is occasionally useful for when you want to overwrite a line of text you have just written. LF, on the other hand, is completely useless. Nobody ever wants to be in the middle of a line, then move down to the next line and continue writing in the next column from where you left off. No real-world program ever wants to do that. Just for curiosity, isn't that what Whisper does, the data file format for Graphite? I remember reading about it in https://aosabook.org/en/v1/graphite.html https://aosabook.org/en/v1/graphite.html I realise this isn't core to the author's point, and I mean the question to learn something rather than trying to be a pedant. I think it uses python byte offset semantics rather than CR, but for all I know the python implementation uses CR under the hood. The article overall is a fun read! I love the idea of trying to identify simple pieces of legacy ideas and clear them out.