3 ms·
One thing that is rarely mentioned, but usually practiced: Unix tools rarely modify its own state. The only way to modify the behaviour of a program is to pass
by II2II 1y ago
One thing that is rarely mentioned, but usually practiced: Unix tools rarely modify its own state. The only way to modify the behaviour of a program is to pass parameters, set an environment variable, or modify a configuration file. This lends a great degree of predictability to how programs will behave. If you pipe something into grep, sed, awk, etc. you know how it will behave. It sounds like the article's author is not just ignoring that aspect of the Unix philosophy, but contradicting it.
I'm not exactly sure what the author is arguing for. Perhaps they have a vision, and perhaps it is a vision that has utility. That said, I do not see how their words fit into a modernized version of the Unix philosophy.
- nalaginrut 1y agoYou mean functionality as in functional programming? I wonder if it aligns with Unix philosophy. But that's an interesting insight.
- II2II 1y agoIf true, I'll leave credit to that insight to you since I was not thinking in terms of functional programming. I don't know enough about functional programming to assess whether it is true, but piping data through the classic Unix utilities does seem to meet at least one criteria of functional programming (e.g. the utilities act as pure functions).