>#CURRENTYEAR >#2017 >windows still can't into

>>60788830
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

File: 1495568173469.jpg (159KB, 639x827px) Image search: [Google]

159KB, 639x827px

>>60788910
>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.

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

>>60788932
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.

>>60788830
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.

>>60789004
"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.

>>60789040
>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.

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

Do people actually do this?

There is no hope for people like you

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

>>60789095
really offers the best explanation imo.

>>60788830
BACKWARD COMPATIBILITY

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

>>60789095
>>60789112
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

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

>>60789099
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

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

>>60789141
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

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

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

Case sensitivity in file names is retarded.

>>60788830
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)

>>60789146
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.

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

>>60789146
I know you are sorry.

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

>>60789216
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.

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

>>60789233

this >>60789243

>>60789243
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.

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

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

>>60789287
>your average person needs to manage YouTube's dbs

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

>>60789300
youtube server needs that feature
average person needs youtube

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

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

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

>>60789405
to me thats a transitive relationship

>>60789465
There's such thing as direct and indirect needs

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

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

>>60789611
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.

>>60789665
>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

>>60789707
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.

>>60789779
>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.

>>60789779
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.

>>60789804
>>60789916
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.

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

>wanting case sensitivity

>>60790243
What sort of helpdesk supports newfag Linux users?

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

>>60790269
This thread is about Windows

>>60790310
>using the command line in Windows
lol

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

>>60790374
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.

>>60790255
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?

>>60788944
average stallmannberg cultist

>>60790409
>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.

>>60790409
>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

>>60790492
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.

>>60788830
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

>>60790553
I refuse to believe this.

>>60790409
>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 ?

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

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

>>60790662
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.

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

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

>>60790723
it's a DOS limitation that made it into NT

>>60789215
>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?

File: 2017-06-07 12_37_37.png (24KB, 639x581px) Image search: [Google]

24KB, 639x581px

>>60790566

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

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

>>60790867
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.

>>60790918
>what is tab completion
>what is autocorrection

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

File: asd.png (19KB, 614x504px) Image search: [Google]

19KB, 614x504px

>>60790867
Works for me senpai

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

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

>>60788944
But it gets all the games.

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

>>60790974
>>60790982

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?

>>60791015
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.

>>60790918
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.

>>60791033
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

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

I feel bad for you

File: 2017-06-07 13_27_44.png (23KB, 737x560px) Image search: [Google]

23KB, 737x560px

>>60791080

motherfucker

The swedish language a shit

>>60791285
>2 different letters
>equal
Ahahahahaha, oh wow!

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

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

File: sweden1.webm (3MB, 1280x720px) Image search: [Google]

3MB, 1280x720px

>>60791285
ahahahahha

>>60791353
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.

>>60788830
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.

>>60791482
>nfsadmin server [ ComputerName ] config casesensitivelookups=no

Woops got yes, no backwards.

>>60791482
and that command does exactly what ?

>>60791502
creates mustard gas, stay away!

>>60791502
Enables case sensitive lockups by the OS. Allowing OP to have both his little dick and someone else's big DICK in the same folder.

>>60791528
>Enables case sensitive lockups by the OS
doesn't that only apply to NFS shares?

File: nimetön.png (17KB, 672x479px) Image search: [Google]

17KB, 672x479px

>>60791285
If it makes you feel better: Finnish version has the same issue as well. Well, at least it sorts muh special snowfake letters correctly.

>>60791482
Is there a command that stops windows from freaking out when there is a folder named aux or con?

>>60788830
what did you expect from software made by couple jews and pajeets?

>>60791558
https://breakthesecurity.cysecurity.org/2011/04/why-can-not-we-create-con-folder-in-windows.html
If only you'd be able to use Google.

File: GIF.gif (293KB, 690x505px) Image search: [Google]

293KB, 690x505px

>>60791558
>>60791667
Windows 7 SP1 Ultimate x64 doesn't have this problem

File: intel has hardware backdoor in their processors (100).jpg (79KB, 571x542px) Image search: [Google]

79KB, 571x542px

>>60791358

kek

File: 1471397936803.jpg (44KB, 481x554px) Image search: [Google]

44KB, 481x554px

>>60790390
What?

File: 1496695713697.jpg (54KB, 620x465px) Image search: [Google]

54KB, 620x465px

>>60791142
>console

File: c5713139f549df845b3036f73dc6ce8d.jpg (196KB, 1600x1150px) Image search: [Google]

196KB, 1600x1150px

>>60790553

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

This is what happens when you developers are Indian. They can't tell the difference between 'V' and 'W' either so they made sure Windows couldn't.

>>60789099

class Fuck:
    pass
fuck = Fuck()

>>60792021
That's because Swedes don't differ "V" and "W", meme moron

>>60792507

Its a joke, Prakjeet. Don't get offended. Also you're incorrect.

>which file to delete
>delete the dicks.txt
>nigga they all dicks.txt!!

>>60792737
>i was pretending

>>60788830
>why does anyone still use this pile of garbage?

It's there for legacy reasons, i.e. it's one of the reasons companies still use Windows.

There are few people who use file names that only differ by case-sensitivity (and if you are, you're retarded).

>>60793337

Yeah, because I honestlythought Indian engineers at Microsoft who couldn't pronounce 'v's and 'w's in the correct words modified the actual OS to not recognize the difference between them. Fucking retard.

>>60790422
i like to think that every stalled man posts are him himself

File: 1495501121617.png (33KB, 800x500px) Image search: [Google]

33KB, 800x500px

>people seriously think others actually are fighting for case sensitivity

>>60788830

>Case insensitive filesystem, case insensitive API
that's fine
>Case sensitive filesystem, case sensitive API
that's fine too
>Case sensitive filesystem, case insensitive API
Pure evil.

>>60788944
Thanks for the new wallpaper, friend

>>60789136
>not using zsh so that your tab completion ignores case
Wow it's like you enjoy things not working

There are exactly zero (0) situations where case sensitive filenames would be preferable to more descriptive filenames.

File: 1495350468914.png (219KB, 355x422px) Image search: [Google]

219KB, 355x422px

case sensitive file names are fucking retarded

>>60790936
A resource hog

>>60788830
It's actually more effort to make it case insensitive

>download DOOM.WAD
>open terminal
>sha256sum doom.wad
>"doom.wad: No such file or directory"
>sha256sum DOOM.WAD
>it works

I actually uninstalled linux and switched back to Windows 10 because of this.

>>60788964
What happens if I mount an NTFS partition in Linux and create case differing files and mount it in Windows?

>>60799745
I don't know about case sensitivity but I once created a directory with forbidden symbols that way and it worked on Linux but then the directory couldn't be open, deleted, or renamed on Windows so I had to boot back to Linux just to remove a single symbol from the directory name.

File: 1462423514290.gif (493KB, 440x330px) Image search: [Google]

493KB, 440x330px

>dude case sensitive filesystems should be the standard lmao
>only justification is made up bullshit "dicks.txt would contain male dicks but Dicks.txt would contain female dicks!"
Embarrassing

>>60799661
>Being this butthurt over filename case sensitivity to switch to NSABotnet 10

>>60788830
>windows
You mean Windows API.
NT is perfectly capable of thath.

>>60799573
Autocompletion is a resource hog? What are you running on, a Pentium II?

>>60800658
Better justification: 'A' and 'a' are not the same character. If you aren't autistic enough to appreciate this fact then fuck off to Windows.

File: 1482783597496.png (346KB, 500x464px) Image search: [Google]

346KB, 500x464px

>>60788830
>

date +"%Y"

>still posturing yourself as a tech-savvy person when your use case is so basic bitch that literally all you can do is complain about trivial platform idiosyncrasies that mean nothing to people who actually know how to use a computer while you spend 90% of your computing time in a web browser
>>60803180
>thinking this is an actual justification and not just pointless bikeshedding from a faggot whose computing knowledge can be summed up in a couple Arch wiki pages

File: fa51307b-f233-49ea-b719-cad5bcf1853b..png (260KB, 483x368px) Image search: [Google]

260KB, 483x368px

>>60803243
>>thinking this is an actual justificati
> on and not just pointless bikeshedding
> from a faggot whose computing
> knowledge can be summed up in
> a couple Arch wiki pages

Whoa dude nice projection, there's no need for you to be this assmad over people not liking filesystems making extra decisions for them. Case sensitivity should be mandatory in every respect at all times.

File: bedicked.png (375KB, 535x404px) Image search: [Google]

375KB, 535x404px

>>60788830
When one dick gets confused with another; I hate when this happens.

It's just a preference. I prefer case insensitive because it makes everything way simpler

>>60801529
Implying that the TLAs aren't the major contributes to linux.

File: 1468689800005.png (8KB, 277x271px) Image search: [Google]

8KB, 277x271px

>>60805594
>Lawl Loonix is botnet 2!