Be on Windows

>be on Windows
>cloning git repo fails
>filename collisions because of case insensitive filesystem

Attached: trfd.jpg (850x800, 379K)

Other urls found in this thread:

cygwin.com/cygwin-ug-net/using-specialnames.html
twitter.com/NSFWRedditImage

Other than understanding your frustration, I have good news for you.
cygwin.com/cygwin-ug-net/using-specialnames.html
Go to
>Case sensitive filenames

Name 1 (one) reason why a file system should be case sensitive.
You want to have two folders inside a folder. One called Benis and the other one benis?

Attached: 1542906409640.jpg (240x219, 16K)

to avoid locales clusterfucks

>case sensitive branch names
Even if the Windows supported case sensitive filenames, it would still be most retarded idea ever.

Create an issue on the repo, or better a pull request renaming one of the files to an alternative that works on case-insensitive filesystems.

Whether you're working on a case-sensitive file system or not, having conflicting filenames like that in a code repo is probably an oversight.

>work in a C# shop
>use git on VSTS for work control
>coworker does a bugfix, then refactors around
>notices incosistency in folder naming and fixes it so that all is in pascal case
>Visual Studio notices it as a rename
>git on the server creates a new directory with a fixed name along the prev one
>some files land in first dir, others in the second one
>nobody notices, because on their local copy all gets written in the same directory
mfw this shit happens once every quarter

Case sensitivity is dumb.

Because for a computer B and b are something completely different.

>having conflicting filenames like that in a code repo is probably an oversight
it's userspace of an unixy operating system
some of the conflicting filenames are base64 encoded strings

NTFS actually supports case sensitivity, it's the win32 API that does not

I agree that there's no practical purpose, but having case sensitive filenames is more 'correct'.
The ideal filesystem would be case sensitive for referencing files but not allow identical filenames with varying case.

Letting programmers create scripts where ./MyAmAzInGfIlE and ./myamazingfile refer to the same file is retarded, but allowing two separate files with those names to exist in the same directory is equally retarded.

>filename collisions because of case insensitive filesystem

If you are naming two files the same, but with different case then you deserve to be shot and burred in a shallow grave.

performance

>be on windows
>cannot move file, file path is too long
>cannot delete file, file path is too long
Fuck this meme OS

>be on windows
>create folder named 'con'
>cant

>do this on purpose
>winfags literally unable to contribute
>pull request quality skyrockets

Attached: 1489353138960.jpg (470x595, 201K)

Fiendish and crimsonpilled

>allowing two separate files with those names to exist in the same directory is equally retarded
No it's not, you retarded winbaby. How about you stop sucking on daddy microsoft's teat and grow a brain.

it is retarded, you can't interact with one of them yet it's valid for it to be there

>What did he mean by this?

Attached: Screenshot_2019-01-15_19-40-42.png (1920x1080, 284K)

File names exist solely for interfacing with users, otherwise we might as well use numbers. There's no point in making something more error prone because muh purity.

Just fuck off, windows does loads of shit different for no good reason.
Why do mac addresses use - on windows? Who fucking knows.

Because it doesn't make any god damn sense and file systems were CREATED for use by programmers. You are just moving the "error prone" problem.

Case-insensitive file systems are a relic of the pre-autocomplete era. Prove me wrong.

Ackhchyually ntfs is case sensitive, it's windows explorer that isn't. Who are you trying to fool here.

I was working at a company using C# and when they switch to .NET Core (multi-platform implementation of ASP.NET) I had to chase down some horrible case insensitive file system bugs. And we were using the whole M$ MVC shebang.

This is labeling for humans though. And not even autistic humans like developers, but normal assholes who use their filesystem to store files.