Re:APFS is not safe to use with names which have Unicode nor...
by deong on Wednesday June 07, 2017 @03:01PM
(#14508977)
In that case, I agree. The problem here seems, from my understanding, to be that what Apple did was more like
app -> CFFile -> unicode normalization -> fopen -> APFS
which screws you because anyone can just call fopen on their own without using the core foundation libraries, leading to inconsistent states in the filesystem. You can be higher level than the filesystem, but only a little bit. You can't be higher level than some API that developers will regularly use (unless you do like ZFS and normalize at lookup rather than create).
What I mean is that unicode normalization is really hard, and it should be it's own module that can be used regardless of the fs.
app->fopen->unicode normalization->APFS/HFS/FAT...