When I switched to OS X from Linux, case sensitivity was a thing I missed dearly. I know that it's a fringe feature, and that even I don't use it much, but it irks me that it isn't there, especially when both ext4 and NTFS have it.
It's more important considering Time Machine backups and actual UNIX moving and copying of files, and this is also where resource/data forks are also a huge burden. Unless OS X implements a different cp and mv than the standard FreeBSD ones, just implementing a filesystem without forking could be a solution. Also, case sensitivity is affected the same way.
For the normal user, it's fine to keep a case-preserving filesystem. But, Apple needs to make sure developers write their apps with case-sensitivity in mind (I'm looking at YOU, Adobe).
NTFS "has" it, but it's only there to meet POSIX requirements. It's merely case-preserving in non-POSIX contexts, which ultimately means almost nobody uses it.
Unless OS X implements a different cp and mv than the standard FreeBSD ones, …
It does (though it didn't before 10.4). There's still lots of code out there that doesn't respect them, no doubt, but to my knowledge you can use the built-ins without worrying about losing your resource forks.
It's more important considering Time Machine backups and actual UNIX moving and copying of files, and this is also where resource/data forks are also a huge burden. Unless OS X implements a different cp and mv than the standard FreeBSD ones, just implementing a filesystem without forking could be a solution. Also, case sensitivity is affected the same way.
For the normal user, it's fine to keep a case-preserving filesystem. But, Apple needs to make sure developers write their apps with case-sensitivity in mind (I'm looking at YOU, Adobe).