Is It Unix?

The day Linux gives the Mac diagnostic that you can't open a file because you don't have the application is the day Linux becomes non-Unix.
 - Doug McIlroy

1. HFS is not POSIX-compliant.
2. HFS cannot understand that a file may have more than one name.
3. Users are afraid to defrag a disk because HFS is considered wobbly.
4. HFS has /.vol.
5. There is no real file manager.
6. There is no integration with the Unix subsystem, much less enhancement.
7. Users are deliberately kept in the dark about security issues.
8. There are non-portable streams (resource forks).
9. There are 'catalog file' data which corrupt end use.
10. Finder does not alert the user to resource forks.
11. Users cannot always send files to friends on other platforms.
12. Unix compression utilities do not see resource forks.
13. Unix does not see resource forks.
14. A great many Apple utilities create Desktop DB and Desktop DF.
15. Secure areas of secure disks are accessible from MacOS.
16. Apple keep MacOS installed on every new computer.
17. There are .DS_Store files all over the place.
18. There are over twelve thousand useful Unix files and utilities that are installed on every OS X disk and then deliberately kept hidden. Most users don't even know they're there.
19. Finder and the file dialogs hide the following in root from the user: .vol, automount, bin, cores, Desktop DB, Desktop DF, Desktop Folder, dev, etc, lost+found, mach, mach_kernel, mach.sym, opt, private, sbin, tmp, Trash, usr, var, VM Storage, Volumes.
20. The system doesn't like it when you save a file with a 'dot' prefix.
21. Finder and the file dialogs refer to Unix programs as 'documents' [sic].
22. No setuid or setgid or sticky bit information is given by Finder.
23. A user cannot set setuid, setgid, or sticky bits with Finder.
24. Most users don't even know what setuid, setgid, and sticky bits are.
25. Finder does not tell users how much of a file size is its resource fork.
26. There is a secret directory in root that POSIX software can't see so HFS can pretend it's POSIX-compliant.
27. Apple utilities can corrupt the file system because they don't understand hard links.
28. /.vol doesn't understand hard links.
29. HFS doesn't understand hard links.
30. Carbon doesn't understand hard links.
31. Most users don't even know what a hard link is.
32. HFS can't reuse inodes. It has to wait until the entire list is exhausted, then set a flag, then start over from the beginning again and pick the empty slots.
33. HFS sorts directories with binary trees that have three nodes [sic] where the leftmost [sic] node is never used [sic] and the person who came up with this idea was not fired on the spot.
34. When HFS corrupts (and it does right as Seattle rain) users pull out DiskWarrior - for everything.
35. Darwin is not FreeBSD.
36. It's not Unix - it uses something that used to resemble Unix.
37. Cocoa and Apple's Objective-C are not open source.
38. Cocoa and Apple's Objective-C are not open standards.
39. Cocoa and Apple's Objective-C are not eminently portable.
40. Creator codes and file types are ideas by an über-dweeb that's way too attached to his mummy. They lock file associations without the user having a chance to correct potential errors or move outside the system. There is no freedom, only constriction - and all in the name of 'user friendly'.
41. iTunes is Carbon and wobbly as hell; even the iPod is Carbon; even QuickTime is Carbon.
42. Apple hard wired a monstrosity into Unix. It was known as 'MacOS'. The job took seven years - with an OS that had already been ported to other platforms in a matter of weeks or months. Countless marketing opportunities were irresponsibly wasted.
43. Apple don't want you to know you're dealing in files and folders and the old users don't want to know it either. All they want you to see are icons on a desktop.
44. Cocoa drag and drop uses Carbon MacOS FSSpecs.
45. HFS is always losing what it calls 'temporary CNIDs' - contraptions created in a futile attempt to be POSIX-compliant. Users have to boot from their install DVD and correct their corrupt file systems with Disk Utility.
46. There is little or no open standards Unix work on the platform.
47. Users aren't supposed to know what's going on under the bonnet of their OS. Apple don't want them to either.
48. Apple have COLOURS for files; they don't show (or let you set) mode bits but they give you COLOURS.
49. The default 'file manager' doesn't tell you when files are world-writable, or when newly created directories are empty, or when anything happens that from a security perspective might be important to you and a serious danger to your security.
50. Debian and other Linux and BSD users build their own kernels; Apple users don't even know what a kernel is.
51. It's possible to totally corrupt HFS with ordinary Unix programs from a command line.
52. Apple hide iPod songs on what are supposed to be Unix disks with archaic MacOS APIs.