What are these __MACOSX folders I keep seeing in zip files made by people on OSX? Some take as much as 30% of the file.
What program are producing these __MACOSX folder and how can mac users avoid this mistake?
migrated from stackoverflow.com Feb 4 '10 at 1:58
This question came from our site for professional and enthusiast programmers.
Here's a link that explains it pretty well. I suppose it is a bit late to help Yada, but for posterity.
The rest is my opinion:
@nickf: Never seeing these files is not a FEATURE of those OS X versions it is a FLAW. People produce data, wrap it up, store it on different mediums and so on. They need to know what is needed or what is not needed. Hiding it keeps them in the dark.
The age old bad idea of hiding things from users: A programmer, concerned with expediency of accomplishing his own work, abuses something in the domain of the end user, to make it easy for himself.
In this case he stored meta data in the user's data space, he then hid it from the user. He missed the big picture: The user won't become aware of the hidden details. When he packages his 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.
Hiding things from the user is bad. It assumes the user is stupid, when more accurately it is the programmer being stupid, or lazy.
To be clear, this bad habit is not confined to MAC. It is everywhere. 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.
Programmers and vendors: Please keep things in the open. When you you hide them, you make yourself stupid and the user uninformed.
To answer your final question:
Mac OS X users can install a 3rd-party archiving utility like Keka, then tell it to not use Resource Forks, then set it as the default compressor.
How to do this with Keka
Tell Keka to not use Resource Forks
Make Keka the default compressor