Well, both points of view have a point.<p>The central idea of Unix is that everything is a file.  Files are just streams of bytes on disk.  Most happen to be text.  Text is just streams of lines.  And then you write a bunch of simple tools that handle files, bytes, and lines, and they will combine really well for more complex tasks.<p>However this was (and in many corners still is) a radical idea.  The natural tendency in virtually every other system, from the Macintosh to IBM mainframes, was to store data in various structured records.  Whether we&#x27;re talking resource forks or records, you always, always, always add structure of various kinds.  The idea of just scanning through bytes to find, say, the end of a record is shockingly inefficient.<p>So we have the point of the article.  HFS+ breaks Unix.  If you don&#x27;t see that, then you don&#x27;t actually understand Unix.  The filesystem ignores one of the founding central concepts, with the result that the entire Unix toolkit and way of thinking about the world doesn&#x27;t work.  Standard utilities, scripts, etc don&#x27;t know that resource forks exist, and will do the wrong thing with them.  If you walk into OS X and are told, &quot;It&#x27;s Unix under the hood&quot;, well that is a lie.  It really isn&#x27;t.  You can work within it and only do Unix things and it will work, but as soon as you access things from elsewhere in the Apple ecosystem, things break in ways that they wouldn&#x27;t in, say, Linux.<p>But we also have your point of view.  There are very good reasons that HFS+ works the way it does.  And it is integrated into the UI in ways that date back decades.  And THIS is true.  OS X was an attempt to put a Macintosh UI on a fork of Unix.  And preserving central concepts of Unix really were not as important as making the UI work right.  With the same features.  With data being reasonably easy to port between the two systems, and programs not unnecessarily different.<p>Both points of view are valid.  Which one matters depends on what you&#x27;re trying to do.  Furthermore it is natural, not stupid, that a person who has just had a major plank pulled out from under their way of understanding the world tends to have a strong emotional response.<p>&quot;OMG, you broke everything!  The tools that I rely on don&#x27;t work and I have no idea what else is broken!&quot;  This is an extremely common response.  This is one of the reasons why it can be hard for programmers to switch languages and environments.<p>As it happens, I personally understand both points of view.  I have over 20 years of experience with both Macs and Unix.  This is typed on an Apple laptop.  But fundamentally I agree with the article.  Apple broke Unix.  I recognize that there is no solution at this point, and I mostly confine myself to living within the Unixy parts of the system.  But HFS+ got it wrong and is not well integrated with the command line.  I mean look at this.  If you have myfile you can look at myfile.  Then ls myfile&#x2F;..namedfork and get an error.  Then ls $file&#x2F;..namedfork&#x2F;rsrc and see more stuff???  And I can only know to do this if I know it is there to be seen???<p>That&#x27;s just broken.