> but using their weird HFS "resource forks" to do it That’s incorrect. File type and creator code always were stored where they belong: in the file system. A

> but using their weird HFS "resource forks" to do it That’s incorrect. File type and creator code always were stored where they belong: in the file system. Also, what’s weird about alternative file streams? > so that it not only couldn't be implemented on other platforms The main reason it “couldn’t” be implemented elsewhere is because of the dominance of FAT, which didn’t think it worthwhile.