Hacker News Reader

This has nothing to do with binary versus text.

I think it does, insofaras OSs feel free to just fuck with the contents of files they think are text, replacing newlines willy-nilly. Files not identified as text are safe from such automatic tampering.

I've never seen this behaviour at an OS level. This seems like an editor issue, and binary files are not exempt from being messed up by a slightly incompatible editor, far from it.

Perhaps you have been spared from writing code for Windows:

https://learn.microsoft.com/en-us/cpp/c-runtime-library/refe...

> In text mode, carriage return-line feed (CRLF) combinations are translated into single line feed (LF) characters on input, and LF characters are translated to CRLF combinations on output.

Is there a reason I should blame the OS specifically and not the C runtime?

I guess it depends on how specific you want to be. The Windows C runtime is a component of the OS.

Well you're not really supposed to use the OS copy of msvcrt.dll

Yes, library functions do what you ask them to do.

Reply on news.ycombinator.com