<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Whats with __MACOSX in Zip files?</title>
	<atom:link href="http://floatingsun.net/2007/02/07/whats-with-__macosx-in-zip-files/feed/" rel="self" type="application/rss+xml" />
	<link>http://floatingsun.net/2007/02/07/whats-with-__macosx-in-zip-files/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=whats-with-__macosx-in-zip-files</link>
	<description></description>
	<lastBuildDate>Mon, 06 Feb 2012 12:32:40 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Graflgauze</title>
		<link>http://floatingsun.net/2007/02/07/whats-with-__macosx-in-zip-files/#comment-242563</link>
		<dc:creator>Graflgauze</dc:creator>
		<pubDate>Mon, 09 Jan 2012 18:41:55 +0000</pubDate>
		<guid isPermaLink="false">http://floatingsun.net/blog/2007/02/07/793/#comment-242563</guid>
		<description>Sorry yes, that would be the .DS_Store file that is written all over the damn place in OSX-created things</description>
		<content:encoded><![CDATA[<p>Sorry yes, that would be the .DS_Store file that is written all over the damn place in OSX-created things</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mraof</title>
		<link>http://floatingsun.net/2007/02/07/whats-with-__macosx-in-zip-files/#comment-241756</link>
		<dc:creator>Mraof</dc:creator>
		<pubDate>Tue, 03 Jan 2012 20:59:51 +0000</pubDate>
		<guid isPermaLink="false">http://floatingsun.net/blog/2007/02/07/793/#comment-241756</guid>
		<description>Well, that explains that weird folder that I was wondering about.</description>
		<content:encoded><![CDATA[<p>Well, that explains that weird folder that I was wondering about.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Zana</title>
		<link>http://floatingsun.net/2007/02/07/whats-with-__macosx-in-zip-files/#comment-241023</link>
		<dc:creator>Zana</dc:creator>
		<pubDate>Fri, 30 Dec 2011 01:25:29 +0000</pubDate>
		<guid isPermaLink="false">http://floatingsun.net/blog/2007/02/07/793/#comment-241023</guid>
		<description>As someone who recently had to use some Macs for work (after years of coding/scripting/Windows domain management) I have to agree with the author that often the Mac OS behavior is idiotic and NOT &quot;more user friendly.&quot;

To me, needing to issue a TERMINAL COMMAND is HELLISHLY more complex than it needs to be.  It is not &quot;simple&quot; by any stretch of the imagination.  You COULD use Powershell/CMD to do crap like this but the point is that in Windows basic stuff like this is EASY to do and follows LOGICAL, PREDICTABLE steps.

Obviously, as someone who has debugged hundreds of thousands of lines of assembly in IDA Pro, it&#039;s not &quot;hard&quot; for me to use the terminal to show hidden files or create an archive, but I really don&#039;t care about whether it&#039;s &quot;hard&quot; for me.  The point is that it is outrageously harder IN COMPARISON to Windows to achieve the same thing (create a simple Zip file without added thumbnails/metadata).  Using a command line to accomplish things is virtually NEVER easier unless you (a) have a photographic memory (b) there is no other way.  Unix/Linux/Ubuntu did not become more popular/usable by ELIMINATING graphical options.

Saying &quot;oh here&#039;s the solution, just download a third party application to correct the problem&quot; is basically agreeing that Mac has failed to do anything better than the competition, since that is basically how Windows/nix work.  The whole point of Mac is ALLEGEDLY that is does things better/more simply out of the box, but in fact it requires terminal commands to make basic changes...</description>
		<content:encoded><![CDATA[<p>As someone who recently had to use some Macs for work (after years of coding/scripting/Windows domain management) I have to agree with the author that often the Mac OS behavior is idiotic and NOT &#8220;more user friendly.&#8221;</p>
<p>To me, needing to issue a TERMINAL COMMAND is HELLISHLY more complex than it needs to be.  It is not &#8220;simple&#8221; by any stretch of the imagination.  You COULD use Powershell/CMD to do crap like this but the point is that in Windows basic stuff like this is EASY to do and follows LOGICAL, PREDICTABLE steps.</p>
<p>Obviously, as someone who has debugged hundreds of thousands of lines of assembly in IDA Pro, it&#8217;s not &#8220;hard&#8221; for me to use the terminal to show hidden files or create an archive, but I really don&#8217;t care about whether it&#8217;s &#8220;hard&#8221; for me.  The point is that it is outrageously harder IN COMPARISON to Windows to achieve the same thing (create a simple Zip file without added thumbnails/metadata).  Using a command line to accomplish things is virtually NEVER easier unless you (a) have a photographic memory (b) there is no other way.  Unix/Linux/Ubuntu did not become more popular/usable by ELIMINATING graphical options.</p>
<p>Saying &#8220;oh here&#8217;s the solution, just download a third party application to correct the problem&#8221; is basically agreeing that Mac has failed to do anything better than the competition, since that is basically how Windows/nix work.  The whole point of Mac is ALLEGEDLY that is does things better/more simply out of the box, but in fact it requires terminal commands to make basic changes&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan Chokola</title>
		<link>http://floatingsun.net/2007/02/07/whats-with-__macosx-in-zip-files/#comment-238890</link>
		<dc:creator>Dan Chokola</dc:creator>
		<pubDate>Tue, 13 Dec 2011 19:11:29 +0000</pubDate>
		<guid isPermaLink="false">http://floatingsun.net/blog/2007/02/07/793/#comment-238890</guid>
		<description>Disclaimer: I am not a Mac user and actually have a burning hatred for Macs and their fanbase. I came across this webpage trying to figure out just what is in those __MACOSX directories.

There are a couple solutions here. https://discussions.apple.com/thread/1640973?start=0&amp;tstart=0

IMHO, VII hit the nail on the head when he said that Mac is going mainstream. It invalidates the &quot;We are not stupid&quot; point as well. As Mac tries to sell itself to the average stupid user more and more, expect crap like this. Your best bet is to just use the command line, or roll your own script, which were made for the smart user.

The &quot;Redundant&quot; point is a memory/CPU time tradeoff. Rather than have a user recreate this metadata from files, which takes CPU time, it&#039;s stored in the zip file and available immediately to the user after it&#039;s unzipped. There is a legitimate reason for this, then. That said, I agree the metadata could probably be stuffed into the archive somehow that gets ignored by normal zip programs and picked up by the Mac zip program.</description>
		<content:encoded><![CDATA[<p>Disclaimer: I am not a Mac user and actually have a burning hatred for Macs and their fanbase. I came across this webpage trying to figure out just what is in those __MACOSX directories.</p>
<p>There are a couple solutions here. <a href="https://discussions.apple.com/thread/1640973?start=0&#038;tstart=0" rel="nofollow">https://discussions.apple.com/thread/1640973?start=0&#038;tstart=0</a></p>
<p>IMHO, VII hit the nail on the head when he said that Mac is going mainstream. It invalidates the &#8220;We are not stupid&#8221; point as well. As Mac tries to sell itself to the average stupid user more and more, expect crap like this. Your best bet is to just use the command line, or roll your own script, which were made for the smart user.</p>
<p>The &#8220;Redundant&#8221; point is a memory/CPU time tradeoff. Rather than have a user recreate this metadata from files, which takes CPU time, it&#8217;s stored in the zip file and available immediately to the user after it&#8217;s unzipped. There is a legitimate reason for this, then. That said, I agree the metadata could probably be stuffed into the archive somehow that gets ignored by normal zip programs and picked up by the Mac zip program.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Radu Tanasescu</title>
		<link>http://floatingsun.net/2007/02/07/whats-with-__macosx-in-zip-files/#comment-229324</link>
		<dc:creator>Radu Tanasescu</dc:creator>
		<pubDate>Mon, 19 Sep 2011 13:52:06 +0000</pubDate>
		<guid isPermaLink="false">http://floatingsun.net/blog/2007/02/07/793/#comment-229324</guid>
		<description>Well, this is late coming but I just had to type it:

If you are SMART then you shouldn&#039;t ask such a stupid question, read the article again, you&#039;ll figure it out.</description>
		<content:encoded><![CDATA[<p>Well, this is late coming but I just had to type it:</p>
<p>If you are SMART then you shouldn&#8217;t ask such a stupid question, read the article again, you&#8217;ll figure it out.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Newb</title>
		<link>http://floatingsun.net/2007/02/07/whats-with-__macosx-in-zip-files/#comment-225886</link>
		<dc:creator>Newb</dc:creator>
		<pubDate>Mon, 08 Aug 2011 16:18:07 +0000</pubDate>
		<guid isPermaLink="false">http://floatingsun.net/blog/2007/02/07/793/#comment-225886</guid>
		<description>Thanks for the command, it worked like a charm. I could also remove the pesky &quot;.DS_Store&quot; files who somehow sneaked into the Zip.</description>
		<content:encoded><![CDATA[<p>Thanks for the command, it worked like a charm. I could also remove the pesky &#8220;.DS_Store&#8221; files who somehow sneaked into the Zip.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Simon</title>
		<link>http://floatingsun.net/2007/02/07/whats-with-__macosx-in-zip-files/#comment-220027</link>
		<dc:creator>Simon</dc:creator>
		<pubDate>Sun, 29 May 2011 21:11:56 +0000</pubDate>
		<guid isPermaLink="false">http://floatingsun.net/blog/2007/02/07/793/#comment-220027</guid>
		<description>Brilliant! ZipCleaner solved my problem for this issue, recommend it for anybody else in the above thread experiencing the same problem.</description>
		<content:encoded><![CDATA[<p>Brilliant! ZipCleaner solved my problem for this issue, recommend it for anybody else in the above thread experiencing the same problem.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: HZC</title>
		<link>http://floatingsun.net/2007/02/07/whats-with-__macosx-in-zip-files/#comment-217795</link>
		<dc:creator>HZC</dc:creator>
		<pubDate>Sat, 30 Apr 2011 14:35:16 +0000</pubDate>
		<guid isPermaLink="false">http://floatingsun.net/blog/2007/02/07/793/#comment-217795</guid>
		<description>Search for response by HZC for simple solution</description>
		<content:encoded><![CDATA[<p>Search for response by HZC for simple solution</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: HZC</title>
		<link>http://floatingsun.net/2007/02/07/whats-with-__macosx-in-zip-files/#comment-217794</link>
		<dc:creator>HZC</dc:creator>
		<pubDate>Sat, 30 Apr 2011 14:34:19 +0000</pubDate>
		<guid isPermaLink="false">http://floatingsun.net/blog/2007/02/07/793/#comment-217794</guid>
		<description>Here&#039;s a simple solution. Download ZipCleaner from http://homepage.mac.com/roger_jolly/software/ and move the app to your Applications folder. Open the app; it will appear in your Dock. Right-click on the icon in the dock and select the option to keep in dock; close the app.

Now, after you create your zip archive, just drag it to the icon. It will ask you to confirm and then replace your zip with a &quot;clean&quot; zip that you can use on Windows.</description>
		<content:encoded><![CDATA[<p>Here&#8217;s a simple solution. Download ZipCleaner from <a href="http://homepage.mac.com/roger_jolly/software/" rel="nofollow">http://homepage.mac.com/roger_jolly/software/</a> and move the app to your Applications folder. Open the app; it will appear in your Dock. Right-click on the icon in the dock and select the option to keep in dock; close the app.</p>
<p>Now, after you create your zip archive, just drag it to the icon. It will ask you to confirm and then replace your zip with a &#8220;clean&#8221; zip that you can use on Windows.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rlhamil</title>
		<link>http://floatingsun.net/2007/02/07/whats-with-__macosx-in-zip-files/#comment-213685</link>
		<dc:creator>rlhamil</dc:creator>
		<pubDate>Sat, 12 Feb 2011 17:41:06 +0000</pubDate>
		<guid isPermaLink="false">http://floatingsun.net/blog/2007/02/07/793/#comment-213685</guid>
		<description>Please don&#039;t assume what Mac users are like just because you haven&#039;t found any in your office
with a clue.

I&#039;ve been using Unix (the real thing, not the cute
but amateur wannabe Linux) since v7 on the
PDP-11. I don&#039;t think I&#039;ve ever logged into
anything with a GUI without starting a
terminal ASAP - even my iPhone has a local
terminal window (jailbreaks are wonderful).

All metadata is stupid if you don&#039;t want it, and
ranges from useful to indispensable (by existing
apps) if you do.

About half of any given group of people is average
or below. If there are enough people that never
used anything but the graphical console on (for
example) Ubuntu, probably a fair number of them
won&#039;t know what a command line is either.

OS X mostly does its part by having a way
(at the command line) to produce portable
archives either with metadata or without
(although at the present state of affairs, doing
anything useful with metadata is quite nonportable).  It falls short by not including
a GUI way of producing portable archives
either with or without nonportable metadata.

That leaves it to the users to exercise their brains
a bit and either discover the command line or
at least realize they&#039;re doing something that
might not be helpful and track down one of
the ways to extend the GUI to create
unpolluted archives.

I think the real problem isn&#039;t one OS vs another.
The real problem is that anything that starts
out with a shallow learning curve lets people
pick up enough to be more or less useful
very quickly, but seldom offers much incentive
for them to discover more advanced functionality.
Most people are lazy; they don&#039;t read labels or
instruction manuals or anything they don&#039;t
have to.  (Put a MOTD on a timesharing system
way back when, days in advance of an outage,
and notice that it doesn&#039;t reduce the number
of phone calls when the system goes down;
this even with a population of users that log in
just about every day.)

The other problem is when people have only used
one OS, or one mail client, or whatever; esp.
when one person is communicating to many.
When one person is communicating to one other
person, it&#039;s maybe ok if they share the burden.  But
when one person is communicating to many, they
really ought to work harder to produce an efficient communication rather than waste a few minutes of many people&#039;s time with something that overlooks
differences.  (Common example is emailing MS Word docs created with a recent version of Word
when many in your audience still use an older
version that can&#039;t open the new format.)

Sadly I&#039;d expect this to only get worse.  Blogs,
texting, IM, Twitter, and other social networking
sites encourage young users to routinely blurt
out TMI in incoherent fashion.  Unless counteracted
by teaching writing and oral communication for
precision and clarity from an early age on, we&#039;ll
end up with a generation that doesn&#039;t know
discreet from discrete not only because they can&#039;t
spell, but because discreet (and concise) are
concepts completely without foundation for them.</description>
		<content:encoded><![CDATA[<p>Please don&#8217;t assume what Mac users are like just because you haven&#8217;t found any in your office<br />
with a clue.</p>
<p>I&#8217;ve been using Unix (the real thing, not the cute<br />
but amateur wannabe Linux) since v7 on the<br />
PDP-11. I don&#8217;t think I&#8217;ve ever logged into<br />
anything with a GUI without starting a<br />
terminal ASAP &#8211; even my iPhone has a local<br />
terminal window (jailbreaks are wonderful).</p>
<p>All metadata is stupid if you don&#8217;t want it, and<br />
ranges from useful to indispensable (by existing<br />
apps) if you do.</p>
<p>About half of any given group of people is average<br />
or below. If there are enough people that never<br />
used anything but the graphical console on (for<br />
example) Ubuntu, probably a fair number of them<br />
won&#8217;t know what a command line is either.</p>
<p>OS X mostly does its part by having a way<br />
(at the command line) to produce portable<br />
archives either with metadata or without<br />
(although at the present state of affairs, doing<br />
anything useful with metadata is quite nonportable).  It falls short by not including<br />
a GUI way of producing portable archives<br />
either with or without nonportable metadata.</p>
<p>That leaves it to the users to exercise their brains<br />
a bit and either discover the command line or<br />
at least realize they&#8217;re doing something that<br />
might not be helpful and track down one of<br />
the ways to extend the GUI to create<br />
unpolluted archives.</p>
<p>I think the real problem isn&#8217;t one OS vs another.<br />
The real problem is that anything that starts<br />
out with a shallow learning curve lets people<br />
pick up enough to be more or less useful<br />
very quickly, but seldom offers much incentive<br />
for them to discover more advanced functionality.<br />
Most people are lazy; they don&#8217;t read labels or<br />
instruction manuals or anything they don&#8217;t<br />
have to.  (Put a MOTD on a timesharing system<br />
way back when, days in advance of an outage,<br />
and notice that it doesn&#8217;t reduce the number<br />
of phone calls when the system goes down;<br />
this even with a population of users that log in<br />
just about every day.)</p>
<p>The other problem is when people have only used<br />
one OS, or one mail client, or whatever; esp.<br />
when one person is communicating to many.<br />
When one person is communicating to one other<br />
person, it&#8217;s maybe ok if they share the burden.  But<br />
when one person is communicating to many, they<br />
really ought to work harder to produce an efficient communication rather than waste a few minutes of many people&#8217;s time with something that overlooks<br />
differences.  (Common example is emailing MS Word docs created with a recent version of Word<br />
when many in your audience still use an older<br />
version that can&#8217;t open the new format.)</p>
<p>Sadly I&#8217;d expect this to only get worse.  Blogs,<br />
texting, IM, Twitter, and other social networking<br />
sites encourage young users to routinely blurt<br />
out TMI in incoherent fashion.  Unless counteracted<br />
by teaching writing and oral communication for<br />
precision and clarity from an early age on, we&#8217;ll<br />
end up with a generation that doesn&#8217;t know<br />
discreet from discrete not only because they can&#8217;t<br />
spell, but because discreet (and concise) are<br />
concepts completely without foundation for them.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

