The UNIX Philosophy

When I first ran across this book, I thought it looked interesting, but I had a bunch of other books, so I put it aside. Weeks later, back in the bookstore, I noticed it was gone, and was mad at myself for not getting it. Weeks after that, I refound it, and while thrilled, once again rationalized myself into not buying it. I repeated this cycle of frustration/elation every few weeks over the next few months, as I lost and then re-found the book when they rearranged the shelves. After about 3 or 4 iterations, I finally bought it out of frustration. :-) To my surprise, it didn't get lost in the piles of "to read" books. It was a fairly quick (and excellent) read. I have recommended it dozens of times to friends and co-workers. From those who are literally just starting out in Unix, to those who have been Unix system administrators for 15-20 years. Gancarz writes on a multitude of levels, and his style translates well no matter where you are on the Unix spectrum of experience. For people who are just beginning, he says "Ok, so you're a newbie... Here's how we all think, and how we all code. If you understand our frame of reference, all of this will make much more sense."For those who are seasoned, he says "Ok, so you're a hot-shot veteran with 20 years of coding and sysadmin under your belt... Here are some reminders and pointers on how we all think, and how we all code. If you make sure to follow the same basic tenets, you can be assured that your code will interoperate with everyone else's, and will withstand the test of time."This is not a book about how to code. This is a book about *how to think* about coding, and operating system design in general. He talks a lot about the portability of data over systems and over time, and how good programs should work well *with each other*, rather than being designed to work with a human. (Compare the user interface of 'grep' to that of Microsoft PowerPoint. One is designed to interface well with thousands of programs, and one is designed to interface well with thousands of humans, but only a few programs. You can't script PowerPoint. You can't include it inside your own programs. You can't call it up from a cron job at 3am to process data for you. It's designed under a different philosophy.) Just Chapter 4, "The Portability Priority", is worth the price of the book, alone. It succinctly explains why you should choose data portability over efficiency and speed, and also why you shouldn't bother going back to rewrite your old scripts in C or Assembly to eke out that last smidge of speed. (The new computers coming out next year/month/week are going to be 10/100/1000x faster, and so will your code!) And he sings the praises of flat ASCII files for data stores that can be edited on any old text editors, read by all sorts of programs and different operating systems, etc. By contrast, MS PowerPoint doesn't even interoperate well with other versions of *itself* from past years, and will almost certainly not be a

This is a wonderful little book that every software designer should ready every second year. The book stresses the issues that we know, but all too often forget: small is beautiful, every program should do one thing well, use leverage, build prototypes, ...The book also has the classical and wonderful story about the three systems of man. The first system is build by man, he has no time to do it "right". It is a "lean, mean computing machine". The success of the first system leads to the second. The second system is built by experts, the design is by a committee, and the result is a fat and slow system. The third system is built by people who have bean "burned" by the second system. Read the complete great story in the book. For a user of UNIX or a designer of programs in the UNIX environment the book explains the UNIX design philosophy. This is what could be expected. However, software designers of all systems will benefit from reading the book. The UNIX philosophy is applicable and beneficiary to all software systems, regardless of the operating system used.

This is a hilarious book ("winnow out the chaff" using prototypes!!!) that is more about the philosophy of reusable software tools and portable data rather than Unix. (Unix just happened to be the vehicle in which these ideas were delivered...) It takes a fairly radical stand on the so-called basic tenets of the "UNIX Philosophy" but does so more to illustrate its points rather than to work anyone with software biases into a frenzy. This book cuts through hype and approaches software development and design with a pragmatic and timeless sensibility - a methodology book that ignores object oriented programming, Java, the Internet, or any other technology of the day and focuses instead on more universal aspects of software development - What makes code reusable? What makes data portable? What are the evolutionary stages of a killer app? Read this insightful and amusing book!

This book was a gift, both in the traditional sense, and in what it gave to my appreciation of the Unix way of doing things. A friend sent this to me, now I have to figure out a way to repay him.Gancarz manages to put into words the affection I've felt, but never been able to explain, for Unix. Even if you're a member of the other side, one of those who feel like monolithic software is the future, and things like GUI's belong in the kernel, you can still take away from this book some insights into the smaller is better camp.And, if you do believe in the unix way, "The Unix Philosophy" will show you even more reasons why it simply works. It also provides an intellectual sanity check, a measure to judge your current projects against, and a very high standard to aim for.

I've used Unix (and variants thereof) for seven years. I've read hundreds of books about Unix, from systems design to advanced X11 programming. This book provides the fundamentals to understanding Unix on all levels. The Unix Philosophy has made me appreciate Unix like never before; it's totally changed my ideas about programming, program interoperability, and human-computer interaction. You will want to read this book from cover to cover over and over. You'll find yourself using this book as a reference, even though it's not one. The Unix Philosophy is well written, interesting, and insightful. Read this book. :)