DEFAULT FOLDER X ALTERNATIVE WINDOWS

_MACOSX, as you may have gathered, will only be created on a Mac. The technical term for what is contained within this curious folder is a resource fork. So what the devil is the folder called _MACOSX and what can or should I do with it?

DEFAULT FOLDER X ALTERNATIVE WINDOWS

This is a question that comes up a lot, particularly from Windows users. When you hide them, you make yourself stupid and the user uninformed. Programmers and vendors: Please keep things in the open. Weird smelling programmer droppings emerging from under the rug where they were swept. It's a consequence of programmers falling in love with their own schemes and vendors prioritizing their own goals ahead of the needs of the end user. To be clear, this bad habit is not confined to MAC. It assumes the user is stupid, when more accurately it is the programmer being stupid, or lazy. When the user packages their data and ships it somewhere unanticipated by the programmer, missing parts won't get shipped or unknown parts will arrive which neither the user nor the recipient can explain. They missed the big picture: The user won't become aware of the hidden details. In this case they stored meta data in the user's data space, they then hid it from the user. The age old bad idea of hiding things from users:ДЄ programmer, concerned with expediency of accomplishing their own work,ДЄbuses something in the domain of the end user, to make it easy for themselves. They need to know what is needed or what is not needed. People produce data, wrap it up, store it on different mediums and so on. The rest is my Never seeing these files is not a FEATURE of those OS X versions it is a FLAW.

I suppose it is a bit late to help Yada, but for posterity.Д®xplanation of resource fork at Wikipedia Here's a link that explains it pretty well.

Default folder x alternative