Most end-users don't know what a hidden file with a `.` is, would never create one, and don't particularly care for that level of clutter in a directory.
The big problem is discoverability, as you imply.
> all possible options ... nothing is hidden from the user
This is the key bit. Showing all possible options would go utterly against the mac ethos.
Progressive disclosure and a bullet proof user environment are core user concepts on MacOS. In MacOS a user can rearrange nearly every file visable to them, and never break anything.
Windows and Linux clutter up the users environment with files that literally no one will ever care about (1000 library modules and asset files for a binary application?). And yet they are less flexible to user choice. Move application out of the Application folder... boom! Pathing all breaks. Do the same on MacOS no problem.
Displaying hidden files is not generally an end user feature.
I don't think this would be an overly severe UNIX violation? Dot files would still be hidden by default, the extended attribute would just be an override.
Completely disagree. Yesterday I had to figure out how to display hidden files in finder. I had to google it // apparently there is some hidden key sequence of command option control alt hell that toggles it. It is not exposed in menus anywhere and there shortcut it not all obvious. So next week I’ll be googling it again.
Contrast that with most linux UIs and even Windows. Context-menus display all possible options (generally)... nothing is hidden from the user.
Most of my gripes about MacOS have to do with the finder and context menus. They suck.
This is one example of many.