Re:Things you wish you didn't need to know about S3
by Dylan16807 on Friday May 31, 2024 @09:22PM
(#40542040)
Even with only one case, just four characters is enough for a million files. How much benefit are you really getting from case sensitivity?
[ Parent
| on HN ]
Re:Things you wish you didn't need to know about S3
by marssaxman on Friday May 31, 2024 @11:33PM
(#40542662)
Unicode case folding is a complicated algorithm, and its definition is subject to change with updated Unicode versions. It's nice not to have to worry about that.
Re:Things you wish you didn't need to know about S3
by Dylan16807 on Saturday June 01, 2024 @12:48AM
(#40542965)
Okay, but I don't think this has anything to do with the use case JohnFen mentioned or my questions about it.
If your goal is super easy filename generation then you're probably not going to leave ASCII.
And if you do go beyond ASCII for filename packing/generating, then you should instead use many thousands of CJK characters that don't have any concept of case at all. Bypass the question of case sensitivity entirely.
Re:Things you wish you didn't need to know about S3
by JohnFen on Saturday June 01, 2024 @08:35AM
(#40545217)
Enough that I prefer it. If that were the only advantage, I'd only slightly prefer it. But being able to use case as a differentiator in filenames intended for me to read is something I find even more valuable.
A filesystem not being case sensitive isn't a dealbreaker or anything. I just prefer case sensitivity because it increases flexibility and readability for me, and has no downsides that I consider significant.