@donniel said:
The one thing I hate about UNIX based filesystems is case sensitivity. It really pisses me off when teSt.txt is considered different from test.txt, and both can exist in the same directory! I can tolerate case sensitivity in a programming language, but it's ridiculous when imposed on files!I think the opposite. I don't think Windows should treat the two filenames as the same. It just "feels" more right to have the filesystem be case sensitive. However, I can't think of a real-life example of where it fucked me over on either OS.
What does get me sometimes is the difference between how Windows Explorer treats numbers versus UNIX's ls.
If you have file1.txt, file2,txt, all the way to file100.txt, ls will sort them alphabetically, with 10 coming between 1 and 11. Windows Explorer will order them by the number, basically assuming a preceding 00 or 0.
The "solution*" is simple. I always zero pad numbers in file names. That way they're ordered the same in Windows Explorer and ls.
*solution to a problem that's probably only in my head, and I've never heard anyone else complain about.