4 ms·

> Who in his sane mind uses CRLF even under windows? All my source codes are in UNIX format (aka LF only) and I use it consistent under Windows, Cygwin and UNIX

> Who in his sane mind uses CRLF even under windows? All my source codes are in UNIX format (aka LF only) and I use it consistent under Windows, Cygwin and UNIX.. Why make your life harder? Why would you use LF if the focus of the application that you develop is Windows? You make the life harder for these users. :-) Seriously: your argument typically comes from developers who consider GNU/Linux as a first-class citizen as a development or deployment platform, and Windows only as a second-class citizen (assuming that a Windows port actually exists). I can accept an argument like "I, as a developer, don't care about Windows and its users, so all my source code is in UNIX format." This is a conscious, though quite political decision. But an argument like "not using LF makes lifes harder" without a relativization on which premises this claim is build (such as "GNU/Linux and macOS users are much more important for as, and if there exist any users or developers who use Windows, we consider them to be undesired, because they make everybody's lifes harder") is intellectual ignorance.

python-b5 1y ago
Using LF on Windows is really not difficult. Any text editor actually worth using supports both types of line endings - even Notepad has handled this correctly for years now, from what I remember. I've never been caused any inconvenience as a Windows user by files with LF endings. I never use CRLF if I can avoid it; I only will if working on a codebase that already uses it throughout.
Borg3 1y ago
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.
- aleph_minus_one 1y ago
  > 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_Environment https://en.wikipedia.org/wiki/Windows_Preinstallation_Enviro...
  - Borg3 1y ago
    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...

python-b5 1y ago

Using LF on Windows is really not difficult. Any text editor actually worth using supports both types of line endings - even Notepad has handled this correctly for years now, from what I remember. I've never been caused any inconvenience as a Windows user by files with LF endings. I never use CRLF if I can avoid it; I only will if working on a codebase that already uses it throughout.

Borg3 1y ago

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.

aleph_minus_one 1y ago
> 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_Environment https://en.wikipedia.org/wiki/Windows_Preinstallation_Enviro...
- Borg3 1y ago
  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...