From: Robert Klemme Date: 2010-08-17T04:25:33+09:00 Subject: Re: Unix Philosophy in Ruby Programing 2010/8/16 James : > On Mon, Aug 16, 2010 at 9:43 AM, Peter Hickman < > peterhickman386@googlemail.com> wrote: > >> Now that I reflect on this I find that the point where I understood >> the Unix philosophy was when I read the book "Software Tools" by >> Kernighan and Plauger - don't bother with the Pascal edition of the >> book :( Not sure that you get to learn a lot of programming techniques >> from that book these days (in the old days, the 70s in my case, there >> were few usable programming texts). But the underlying "small tools >> joined together like lego to build something bigger" outlook was an >> eye opener for my - being as I was a mainframe programmer. >> >> Unix was so cool in how it didn't care about things it didn't care about. >> >> > What's neat is that the core unix philosophy of small tools working together > with clear interfaces is a great example of clean object oriented > principles. Modularity, well-defined roles and interfaces, each section of > code doing one thing with no side effects, it's all just great design at the > end of the day. Not all Unix tools are free of side effects or can have side effects under certain conditions: tee, mail, awk variants, perl, python, ruby, dd, find, xargs, rm... Cheers robert -- remember.guy do |as, often| as.you_can - without end http://blog.rubybestpractices.com/