The Art of UNIX Programming

This text reveals the software design secrets of the original Unix designers, showing how they produce software that is fast, portable, reuseable, modular and long lived Luminaries including Brian Kernighan, David Korn and Henry Spencer contribute to the book.
The Art of UNIX Programming This text reveals the software design secrets of the original Unix designers showing how they produce software that is fast portable reuseable modular and long lived Luminaries including Brian Ker

  • Title: The Art of UNIX Programming
  • Author: Eric S. Raymond
  • ISBN: 9780131429017
  • Page: 222
  • Format: Paperback
  • 1 thought on “The Art of UNIX Programming”

    1. This book is about programming. Still, there is almost not a single snippet of code in this 500 page book. Instead it focuses on the philosophy that has developed within the UNIX community over the years. There is a lot of knowledge to be found here, even if you don't develop for, or even like UNIX systems. It has got comments from early UNIX hackers, even some of the original creators, which enrich the text and gives a broader perspective on things in some cases.The fact that many sections incl [...]

    2. Good book. There were a lot of things in here that I've felt for a long time but was not sure how to explain. For example, the discussion of why config files should be human readable made me realize why I was so opposed to an advisor's suggestion that our config file be a giant ugly s-expression on a project I did last year; it also made me realize why I felt that the backend for that project should use sockets to communicate with the GUI (because it encourages modularity, keeps GUI code out of [...]

    3. Victory!!! I have finally completed this book. The book weighs in at just under 500 pages, but it reads much longer than that (at least for me) I don't want to imply that that is negative though, the book is wonderful, and is an absolute must read for any software developer. It just took me 3 months to read, which is significantly longer than I would have thought, or originally wanted.This book does a very good job of explaining the culture and history of unix, but all of those cultural and hist [...]

    4. The history section alone is worth it. Nathan Marz's mantra of "first make it possible, then make it beautiful, then make it fast" clearly were taken from this philosophy. A nearly identical mantra is stated in the first pages of this book.History is doomed to repeat itself.I first read the chapter on Textuality, and have since gone back and started from the beginning. So far this book is excellent.

    5. Curiously Raymond managed not to read Gancarz's classic The Unix Philiosophy while writing this. It doesnt cover quite the same ground, and is much less concise. Its bigger on scripting languages and other more recent developments.

    6. A wealth of knowledge from the first UNIX epoch on a broad variety of systems analysis and design issues. The author's opinions are sometimes laid on rather thickly.

    7. Great insights into some of the historical roots of Unix and its successors, as well as some deep dives into the design of many classic Unix programs. My only complaints were that there was a lot of attribution of elegance to interfaces which, in my opinion, are not very elegant (take the make system or fetchmail configuration for example), and that large sections of the book are dedicated to technologies which are a bit outdated these days. Otherwise, this is a very interesting read.

    8. This book is more about the learnings/lessons from Unix world. Mostly historical descriptions and why certain choices were made by Unix and how they were revolutionary as compared to other operating systems. Lots of practice case studies are included wherein how and why certain choices were made by certain popular programs were made.A very quick read for me - more of like a refresher -as I was already well versed with the historical developments.

    9. This is an awesome book and it will make you question your approach to coding. I'm not saying that it changed my mind about OOP or writing integrated applications, but it did influence me. This is a well-written book seemingly written by a "grumpy old man", but I feel that it gave me a lot of perspective I wouldn't have had otherwise.

    10. (Read online version.)Not bad, but more than enough dated at this point (finished in 2004 and most of it is more relevant to before then) that I'm not sure how much is worth reading. The CLI material is as worthwhile as ever, but the GUI parts are totally obsolete. The case studies are also rather too brief.

    11. Some concepts and ideas are outdated in 2016, making sections of the books irrelevant. Still, the books provides a valuable historical context to the development of Unix and its open source spirituals descendants (Linux, FreeBSD, etc.)

    12. Even though the book is the Art of UNIX programming, this is not a text about programming, but about the philosophy of the UNIX/LINUX OS, their history, architecture, main tools, their principles Good to read it in case you are a user of LINUX

    13. Smart people can be wrong in the details, but not in general. It's not so easy to follow simply formulated UNIX philosophy, but surely required for real programs, that have not to rewrite from scratch, but evolve through ages.

    14. Clear language and thought process. Well written and presented. Includes relevant examples. Organization and chapter layout is non-sequential, thus making book navigation easy and quick to refer. Excellent guide.

    15. You might or might not like Eric Raymond, but that does not make this book any worse. This is a nice summary of the basic principles of the design of Unix and Unix applications, but most of the advice presented there is not limited to a single operating system or a single type of applications.

    16. Took me a while to finish, but very worth it. Great explanation of unix culture, practices, and history. Lots of information to digest but will serve as a good reference for my projects moving forward in the open source world.

    17. Knowing merely the programming tools, languages and utilities in Unix is not sufficient. Unix is a culture and to really exploit it, requires a Unix mind-set. Embrace the culture! Live the culture!This is a MUST-READ book for anyone who is serious in a career based on Unix!

    18. Textuality, Do-one-thing-well, Cheap process-spawning cost, Opensource 커널 소스 한줄 더 보려고 노력하는 것보다도 수많은 OS 중 Unix(Linux)가 지금까지 살아남아 더 번성하게 된 배경과 그 철학을 이해하는 게 우선이다. 다소 편향적이긴 하지만 두번 정도는 더 읽어봐야 될 거 같다.

    19. While suffering from having no residential Internet access for eight days, I did a lot of things in order to kill time. One such thing was reading this book which has been sitting on my shelf for eons.

    20. Reading this from ESR's website as a CS undergrad was a formative experience. It is true that the world has moved on in many respects since this was written, but I enjoyed the historical context nonetheless, and have been arguing for human-readable formats ever since (performance be damned).

    21. Узнал слишком мало нового из этой книги, надо было читать её лет 6-7 назад.

    22. The book would receive a higher rating had the author not stooped to proselytizing. It is reasonably informative, however.

    23. The book is good, but written in a manner that does not really impress me. Apart from that there are many interesting facts and thought-provoking ideas in the book.

    24. Algo arcaico. Interesante para los amantes de Unix / Linux. Tiene conceptos útiles a la hora de programar (y entender Unix).

    25. It got me at the beginning. It gave very good advice… but the latter chapters where a little bit boring.

    Leave a Reply

    Your email address will not be published. Required fields are marked *