News for hackers. Stuff that matters.
Re:Applying the Unix Philosophy to Object-Oriented Design by rm999 on Wednesday November 28, 2012 @10:30AM (#4842969)
>Unix philosophy has nothing to do with objects.

I'm pretty sure it's an analogy.

> It is about interfaces, streams and common intermediate data representation

And this is what modularity is all about too.

> There is nothing from UNIX Philosophy there, just a modularity

Read the second paragraph: http://www.linfo.org/unix_philosophy.html

Re:Applying the Unix Philosophy to Object-Oriented Design by dschiptsov on Wednesday November 28, 2012 @10:37AM (#4843015)
a system that is composed of components (i.e., modules) that can be fitted together or arranged in a variety of ways. - So, it is not just about modules, it is mostly about the glue.

In the same way, Lisp without an underlying list structure is just a prefix notation.

Re:Applying the Unix Philosophy to Object-Oriented Design by pignata on Wednesday November 28, 2012 @11:01AM (#4843163)
I was using the analogy of the composability of Unix tools as a role model for how to think about the segregation of roles in an object-oriented system. I agree with you that the ways in which we can couple these objects together through their interfaces is the core of what we're designing. I think this philosophy as an analogy (especially as outlined by ESR) is applicable to a wide variety of things beyond even programming. Interesting to think about, anyway. Thanks for your thoughts.