Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Oh, its simple. There are many many flavors of UNIX and only one Windows. Hence, I see LF as more portable way to store source code, thats why it is prefered. Additionally, im heavy CLI user so again, more geared toward UNIX systems.

If you develop on windows and only for windows, use CRLF all the way. Just do NOT forget to set .gitattributed correctly, and you are set.



> There are many many flavors of UNIX and only one Windows.

With ReactOS, there even exists a flavor that is not developed by Microsoft. If you consider Wine and its derivates as an implementation of the WinAPI, you have one additional (or multiple if you consider their derivates) implementation of the WinAPI.

Even if you only consider the flavours of Microsoft Windows that are full operating systems, you immediately get multiple ones:

- the discontinued Win 9x series

- the discontinued Windows CE, Windows Embedded CE, Windows Embedded Compact, Windows Mobile, Windows Pocket series (technically quite different from both Windows 9x and Windows NT)

- Lots of variants (indirectly) derived from Windows NT:

* Windows (desktop OS)

* Windows Server

* Windows IoT (I would claim that at least for the Windows 10 IoT Core version, the user experience is quite different from both desktop and server Windows)

* Windows PE [1]

* Further discontinued variants such as Windows Phone

[1] https://en.wikipedia.org/wiki/Windows_Preinstallation_Enviro...


The only valid reason you mention here are legacy Windows, like 9x series. Anything NT based is happy with LF only if you have right tools.

I never touched ReactOS, but I suspect is modern enough to handle LF only too. It was targeting Win2003 AFAIR.

So yeah, I stand corrected abit. If you develop only for windows (especially legacy), use CRLF. Anything w/ portability in mind, go for LF only...




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: