#CURRENTYEAR

>#CURRENTYEAR
>#2017
>windows still can't into case sensitive
why does anyone still use this pile of garbage?

Literally don't give a fuck.

Well until they switch to another file system it won't be possible

But ReFS isn't bootable so they're fucked

>using windows
>admitting you >Literally don't give a fuck.
and this is how freedoms are lost. by believing the false songs of proprietary software

>case sensitive filesystems are a good thing
What the fuck? That shit is just a pain in the balls.

ACTUALLY it's the winapi that's case insensitive. NTFS itself is case sensitive.

NTFS supports case sensitive file names, it's just Windows that has issues with them. You can use Linux to create two files with "same name", it'll save just fine but will cause issues on Windows side

Case sensitive file naming is retarded retarded.

In what case is a good idea to have File.ext and file.ext in the same directory. What information does the casing conveys about a file?

It was a mistake that macOS and Windows fixed, but Linux kept it and now it's too late.

1. Why the fuck would you need two files of the ``same name'' as someone already put it.

2. Why is Dicks (2).txt an issue?

C. If you open the Task Scheduler and press down and tab as soon as it opens, it will crash.

4. I use Windows because I find it fun.

"F" isn't the same as "f." They're different symbols. They may be the same letter, but one is different than the other. Hence, one is capital while the other is lower case. In that context, they can mean, relate, to different things.

Kinda why in writing everything isn't all CAPITALIZED or lowercase. We use a mixture to imply, state, or mean different things.

>1. Why the fuck would you need two files of the ``same name'' as someone already put it.
Well to give an example...
>dicks.txt
could contain links to photos of penises that are composed of individuals who identify as their assasigned sex at birth. Genuine men. While...
>Dicks.txt
Can contain links to photos of chicks with dicks.

They both offer dicks, just different kind of dicks. Hence dicks.txt and Dicks.txt.

>fuck.txt
>Fuck.txt
>FUck.txt

Do people actually do this?

There is no hope for people like you

>fuck.txt
meh kind of fuck
>Fuck.txt
things are starting to get serious
>FUck.txt
shits going down now boi

really offers the best explanation imo.

BACKWARD COMPATIBILITY

computers do.
there are situations where you want to let a program generate filenames or use hashes as filenames

If the best explanation is a shitty one, I am not surprised that Microsoft doesn't think it is an important issue.

>Linux still cant into non-case sensitive files
>have to type the explicit name, capitalization and everything when CD'ing

They both have their problems desu

Seeing how windows has functioned for years without this ability it's not really needed

it's more common for files and directories having the same name and people either start the filename or the directory name with an uppercase character

I'm sorry you're too incompetent to understand the difference and importance between upper and lowercase symbols.

ok, you are right. theres probably no reason to use it in windows, it was just an general answer where such a feature is needed

Just wait till you try to name a file COM or AUX with no extension.

>x is needed for y to function
>y functions without x
>x is needed
??????

Case sensitivity in file names is retarded.

the only argument I've seen that seemed remotely valid against case insensitivity was something to do with localization, and I can't even remember it
To the vast majority of people, Hello.TXT and hello.txt are the same filename, capitalization doesn't really matter to people regarding names in general, if you write "BILLY HERRINGTON" on your paperwork at the doctor's vs "Billy Herrington", it's not like the doctor is going to get confused. Neither should the machine.

>hashes as filenames
encode your filenames differently
the filename is not for arbitrary data (on a semi-related note, there's a damn good case for linux to make leading dashes in filenames invalid)

Why is the difference relevant to the user?
In what world is a file named the same thing, with different capitalization being the only distinguishment good design? Filenames are not for arbitrary data, and anyone who thinks they are is retarded. They are for naming files, and capitalization is not relevant in names.

it's not needed anymore because people have given up on using windows on anything that isn't a desktop.

I know you are sorry.

>They are for naming files, and capitalization is not relevant in names.
pretty much every file hoster, youtube, etc beg to differ

Plenty of people use Windows on laptops, what are you talking about?

Windows was made for humans by professionals. Unix was made by two lazy neckbeards who almost got fired for being worthless. Of course they took the easy way out and made filenames case sensitive.

I think he meant desktop as in, not a server or embedded.

this

So basically shit 90% of the user base doesn't care about, and even then 48% of all servers worldwide use Windows server. Clearly this isn't a feature that's required, and if it IS it's handled in Windows server where it's actually useful.

the restriction that filenames are case insensitive were already present in DOS which was literally made by 2 kids in their mothers garage

>Clearly this isn't a feature that's required
but youtube does require that feature.

>your average person needs to manage YouTube's dbs

>48% of all servers worldwide use Windows server
where the fuck did you pull that number from ?

youtube server needs that feature
average person needs youtube

so average person needs that feature too, they just don't know it

No, the average person needs YouTube to use that feature, the average person doesn't have a use themselves for that feature.

Too many things would break if they introduced case sensitivity now.

to me thats a transitive relationship

There's such thing as direct and indirect needs

>case sensitive filesystems
Sure nobody ever regretted it. What could ever go wrong.

There's nothing really wrong with having either way.
The only problem is switching between the two.

No, there's a pretty big issue with having case sensitivity.
Several issues. There are reasons the mainstream OSes ignore case sensitivity, even in cases where they're supported by the filesystem. This is not just about legacy, this is about the 90% people using them and their expectations.
It would be like removing collations from databases and expecting everything to go well.
It would be a fucking disaster.

>No, there's a pretty big issue with having case sensitivity.
which would be .. ?
>There are reasons the mainstream OSes ignore case sensitivity
only windows does, even os x supports case sensitive filenames

Case sensitivity is not enabled by default on mac os.
Can you really not see the issues the pleb would encour with case sensitivity, have you ever dealed with plebs?!
Case sensitivity is only useful to us developers it MUST NEVER get to the general public.
NEVER.

>Case sensitivity is not enabled by default on mac os.
because: legacy
same goes for windows.

>Can you really not see the issues the pleb would encour with case sensitivity
no, and apparently you can't list any issues too.

People hardly use filenames anymore. It's not really an issue for plebs because all they will do is rename the images or name their documents.

I'll chain you guys on a IT support desk and you will have lots of fun to explain old men and newbs about the wonders of case sensitivity. Which nobody fucking gives a fuck about, literally a waste of time. Good luck justifying why is perfectly fine to have more than one file with the same fucking name.

so you still can't give a single fucking example where it would be a problem ?

>wanting case sensitivity

What sort of helpdesk supports newfag Linux users?

Case insensitive, especially on when using the command line, is simply more efficient.

This thread is about Windows

>using the command line in Windows
lol

But we have already determined that Windows doesn't have case sensitive file names.

You have to remember that Windows is still largely based on command line.

Pretty much everything that runs on it effectively runs through command line.

A single example? Are you fucking real?
Confusing files with the same name ? Waste of time matching the case? Case typos? Invalid references because someone capitalized the name? More hiding sposts for malicious programs?
People calling you because it 'doesn't work'? Who in their right mind woukd want a case sensitive filesystem for the general public. Why the fuck would you want to have more files with the same fucking name for stuff used by common people?

average stallmannberg cultist

>Why the fuck would you want to have more files with the same fucking name for stuff used by common people?
/path/to/directory/ and /path/to/file?
../cache/
../Cache

Although this probably wouldn't matter to the majority of Windows users. I doubt a lot of them could tell you what a directory even is.

>save file
>automagically overwrite different file

gee I wonder

letting people name their files is careless, windows should just generate a quirky identifier with a closing emoji. If you try to disagree I win

Windows should create a random file identifier and then just link it to the file name you choose.
Then we can name all our files system32 and it won't matter, only the system32 linked to the the actual directory matters.

Case insensitivity does not really bother me, having two files with the same name can only lead to confusions.
What does bother me is the ambiguity between \ and / on windows.
Picking one and sticking to it should be a simple decision they could have done a long time ago.
Having the \ as an escape char is really great and I personally prefer to escape spaces than wrapping the entire path in quotes as it is easier to autocomplete.
And the consensus is that / is the folder separation on all other systems, so I don't see why windows needs to be the special case.

>2017
>Windows still can't sort "V" and "W" in file explorer, they just get blended together like they're the same letter

I refuse to believe this.

>More hiding sposts for malicious programs?
thats probably the only legit reason

other than that, windows user just click on whatever file they need when they open it, and just click on save rather than save as.
so
>Waste of time matching the case? Case typos?
wouldn't be an issue
>Confusing files with the same name ?
also, because since they just hit save it saves automatically to the opened file instead of creating a new file


>Invalid references because someone capitalized the name?
since when do windows user create references manually ?

funniest thing is / follows folder structure when connecting to servers //servername/folder but on your host machine is c:\shit\dick

>>automagically overwrite different file
i'm sure windows asks the user if he wants to overwrite the existing file

Often the filename of a file is shown in the title of an application.
"c:\parth\to\work/project/file.cpp" is not just ugly, it is so retarded nobody can take it seriously.

>it is so retarded nobody can take it seriously.
is that the unofficial windows motto ?

Isn't this a win32 limitation not a NTFS limitation?

it's a DOS limitation that made it into NT

>the only argument I've seen that seemed remotely valid against case insensitivity was something to do with localization, and I can't even remember it
IIRC it was about turkish language. They had two seperate versions of the letter i, one with a dot and one without. So when you convert i to uppercase it turns into I with a dot and I in lowercase is i without a dot.

So if you have i.txt and i.txt without dot, which file should the OS pick when you type I.TXT?

here you go. I have searched online but no one seems to be annoyed by this.

I have sorted by name, but it thinks that V and W are the same letter, so only the second letter gets taken into the sorting mechanism.

Bothers the fuck out of me

this can't be real. how would that even work ? what happens if you create a file called "VVx" and one called "Wx" ?

Holy shit
I can't even begin to fathom why this is a thing

If anything it's a good thing.
Whenever I need to navigate to a folder on my raspi, I at first try cd /home/pi/desktop
but turns out desktop doesn't exist. It's Desktop. home is just home though, so it's an inconsistent fuckfest.
When I want to do something through ffmpeg on Windows, I can just type -i c:\folder\subfolder\subsubfolder\file.mp4, I don't need to remember what letters did I capitalize while naming folders. I can even type C:\FOLDER\SuBFoLdeR\suBSubfOLdEr\fIle.mP4 and it will still be valid.

>what is tab completion
>what is autocorrection

are you seriously typing out the whole path + filename instead of just hitting tab ?

Works for me senpai

>Swedish sorting traditionally and officially treated 'V' and 'W' as equivalent
No shit.

If you try to open desktop, bash will autocorrect to Desktop. shopt -s cdspell, my friend.

But it gets all the games.

Should everyone have tanks if the army of their country does?

Could this be because of Swedish language? I'm gonna switch to Engrish and see if it works.

Maybe that's why no one else has complained online?

To be fair consoles has a big number of exclusives so claiming it gets all the games is going too far. The fact is that using only Windows you're limiting your choice of games too.

most shells can have a sort of fuzzy matching enabled for when you make small typos like that

I will agree that caps for folders like Desktop and Downloads is kind of annoying, however I do still very much appreciate case-sensitive stuff.

according to jellinek a state consists of a territory, citizens and an authority.
in democratic countries citizens are the authority
so the countries tanks are the citizens tanks

>getting worse fps in tux racer because the game is linux native

I feel bad for you

motherfucker

The swedish language a shit

>2 different letters
>equal
Ahahahahaha, oh wow!

don't worry, that problem will fix itself.
just wait a few years and the new national language of sweden will be arabic.

>Why the fuck would you need [feature] anyway?
Literally an iPhone tier argument

ahahahahha

The question is whether their codes are the same.
Like the English V and the Swedish V could have different codes, mix them up and throw some Ws in there and suddenly it looks like it's mixing up the letters when it's just sorting them in code order.

Just because it's disabled by default isn't the same as it can't do it.

Start a command prompt with admin rights and type:
nfsadmin server [ ComputerName ] config casesensitivelookups=yes

it's only been like 15 years that has worked for.

>nfsadmin server [ ComputerName ] config casesensitivelookups=no

Woops got yes, no backwards.

and that command does exactly what ?