4 ms·
It does not strike me as a sane design. You already have file extensions, unique prefixes (like those used by the 'file' command to identify files). Why would y
by stefantalpalaru 11y ago
It does not strike me as a sane design. You already have file extensions, unique prefixes (like those used by the 'file' command to identify files). Why would you use fs forks to differentiate between file types?
- ascorbic 11y agoMac OS Classic had no file extensions. I remember they felt like such a hack when switching to OS X, compared to the flexibility of resource forks.
- amyjess 11y agoActually, Classic Mac OS used type and creator codes, which were attributes on files, to identify filetypes, not resources.
- stefantalpalaru 11y agoThat makes more sense.