>2017
>linux is still not case-insensitive
2017
Other urls found in this thread:
support.microsoft.com
twitter.com
>2017
>wants to reduce namespace even further so we need longer names
It has been case sensitive for over 15 years.
Windows fags cant do this:
mkdir Music mUsic muSic musIc musiC
>implying that's bad
>2017
>OP still doesn't realize case sensitive is better
>2017
>OP still represents Linux as a penguin
Hop on the train back to your Reddit camp.
inb4 >gnu/linux
>2017
>linux not cutting their character set by half, dropping the numbet of possible filenames by an order of magnitude
Oy vey
spotted the caselet
True,
ALSO
CAPTCHA: Latina Road
LEWD
itt: Linuxfags who can't code but thinks installing Linux gives them streetcred and makes them l33t and using a useless feature of Linux to boost their ego making them think they're better than Windows users even though.
Don't even lie, you stupid faggots never ran out of characters naming something in Windows.
What happens if you create multiple files with the same name but upper/lowercase, and then load that drive/partition into Windows?
the internet will crash.
You can only access one of the files (in the best case)
>Kode
Fuck off, klossy
Are you retarded? NTFS *is* case sensitive. It's just not consistently utilized across the system because Windows is retarded.
~/.inputrc
set completion-ignore-case on
Happy?
>not telling google it's boao
windowsfags will defend it
cd path\to/folder\fuck/my\shit\up
It's actually worse: you can do that using ntfs-3g on Linux and while it works, it breaks shit on Windows. FAT works as it should for a case-insensitive FS.
>implying having two files with the same name is good practice
>implying you don't name your files
>image.png Image.png iMage.png
I'm only pissed off because Linux insists on sorting things like this:
A.txt
B.txt
C.txt
a.txt
b.txt
c.txt
>not hiding your secret files beneath layers of similar-named folders and files of the same name
>police try to mount your drive on windows
>windows crashes
How is this an issue?
winbabby doesn't know about ascii, that's the issue
>2017
>windows is still not case-sensitive
asciibetical order is simple to implement and doesn't matter at all for computer consumption, but anything being displayed to a human should at least have the option to switch it to case-insensitive alphabetical.
ITT: minor shit that doesnt matter
>minor
It's actually a very sensitive matter.
>2017
>people still refer to GNU/Linux as "linux"
>cannot understand the difference between 'faggot' and 'Faggot'
understandable, as both accurately describe you sir
>1.44MB per floppy
>Normal Floppy read speed: ~500kb/sec
>3711 disks
>2.8 seconds to read each disk
>5 seconds to switch disk and click 'ok' if working quickly.
>total time: 8 hours of switching floppy disks
whew lad have fun
>not using multiple floppy drives and having an intricate machine to auto-load the floppies
you got 3700 floppy drives?
multiple floppy drives mean very little when its only a 3 second read time.
the majority of your time is going to be spent replacing floppys.
I still dont see this being done in under 8 hours unless if you have hundreds, or thousands of floppy drives
4 floppy drives cancel out the switching time by your logic as you can switch a floppy as the next one is being read
file File fIle filE
FiLe FIlE and all other varients have worked in linux for over a decade
leave Programming Penguin alone you brainlet
Ya mount the filesystem windows doesnt support
It will be unreadable and it will tell you that you need to reformat it
this assumes you can average removing, inserting, and pressing 'ok' for each floppy at 5 seconds each.
This isnt happening unless you are literally trying to have an entry in the guiness book of world records
I should try that some day and see how badly windows would behave with something like this.
I just tried this on my linux with a flash drive formatted FAT32.
its a feature of the filing system, not windows.
even on linux if you create Trash.txt and a trash.txt file on a windows-style partition it will ignore the second file creation because there is already a file created with that name
in short, it is the underlying filing system that is case insensitive, not windows.
If you get something for windows that will recognize EXT filing systems it will likely now become case-sensitive with file names when working with that partition
It will never be, it's too late to change it.
Why wouldn't you phrase it "linux is still case-sensitive". Go to /lit/ and learn how to write a well formed sentence without stupid double negatives.