Re: git on MacOSX and files with decomposed utf-8 file names

On Mon, Jan 21, 2008 at 05:53:50PM -0500, Kevin Ballard wrote:

I would go look up specifics to back me up, but my DNS is screwing up  
right now so I can't access most of the internet.

Then you are lucky that your mails reach this ML without problem.

In any case, there  
are 4 standard normalization forms - NFC, NFD, NFKC, NFKD. If there  
are others, they aren't notable enough to be listed in the resource I  
was reading. HFS+ uses a variant on NFD - it's a well-defined variant,  
and thus can safely be called its own normalization form. I fail to  
see how this means it's not "normalization".

The defining property of normalization is producing binary identitical
strings for equivalent strings, IOW, normalization allows you to tell
what strings are equivalent and what are not just by binary comparision.
HFS+ decomposition lacks that property, because strings are not fully
decomposed thus being comparision of equivalent strings may give false
result.

I'm not talking about assigning engineers, I'm saying developing a new  
filesystem, especially one that's proven itself to be usable and  
extendable for the last decade, is something that only smart engineers  
would be capable of doing.

You know, many people still use FAT, but somehow I don't think that
FAT is good despite of it being extendable for more than a decade...
Apparently, HFS+ was not worst part of the Copland project, but I
see no evidence to think that it was developed by the best engineers.

quoted

quoted

And
Copland didn't fail because of stupid engineers anyway. If I had to
blame someone, I'd blame management.

But if the code was so good then why was most of that code thrown away
later when management was changed? Still bad management?

Yes. Even the best of engineers will produce crap code when overworked  
and required to implement new features instead of fixing bugs and  
stabilizing the system. 

I don't think that anyone asked them to implement so much new features.
AFAIK, it was very difficult (nearly impossible) to get anyone to work
on stabilizing existing software and fixing existing bugs in it.

Copland is well-known to have suffered from  
featuritis, to the extent that it was practically impossible to test  
in any sane fashion.

Exactly. IMHO, both management and developers are equally responsible
for that feature-mania.

Bad management can kill any project regardless of  
how good the engineers are.

Sure.

quoted

Byte sequences are not an issue here. If the filesystem used UTF-16 to
store filenames, that would NOT cause this problem, because characters
would be the same even though bytes stored on the disk were different.
So, what you actually lose here is the original sequence of  
*characters*.

I've already talked about that, but you are apparently incapable of  
understanding.

Well, it is *you* who is incapable of understanding anything, even
basic terms as encoding and normalization...

Dmitry