On 08/04/2009 18:11, Jesse Phillips wrote:
Ah, then the problem was using the term "everything is a file." $ ls is unrelated to that philosophy. "Everything is a file" refers to how you communicate to your kernel, not the tools used to manipulate files. That is you can open a text file and use a file descriptor, you open a socket and use a file descriptor. Maybe it would have been better to use the *nix philosophy of "chaining tools together." I've never used powershell so I'm not familiar wit the alternative.
powershell allows chaining tools together... the big thing is that those tools comunicate via .net objects instead of plain text. powershell provides sets of aliases for cmd.exe user as well as unix users, so stuff like
ls | grep exp work out of the box.
