I'm working on a set of tools to do functional programming in Bash (using JSON). I have a pretty good idea of how it's going to be, just need to implement it. Unix pipes are the function application. Json is data structures. And I'll have message passing concurrency like Erlang.<p>If only I didn't have exams! (Been working on it 50% of the time though.)
A similar article about relational 'thinking' with bash scripts <a href="http://matt.might.net/articles/sql-in-the-shell/" rel="nofollow">http://matt.might.net/articles/sql-in-the-shell/</a><p>Like when people shed a "new" light on seemingly simple tools.
As much as I'd like to read this article, Blogspot's themes are so aggressively reader-hostile that I simply cannot.<p>Please, people, if you're using Blogspot, stop. Or at the very least, avoid the craptacular "dynamic" themes like the pox they are.
Just for the record the initial proposed solution is not really an optimal way to do it, specially if log files are huge. Using cat will push the whole log file to stdout first and it's not really needed because `grep GET /var/log/nginx-access.log` will do exactly the same, but way faster.
Interesting to see him describe everything in terms a database. I sometimes think I am too stuck in a relational mindset to understand the reasons for things like MongoDB. Then other times I think NoSql movement is a huge step backwards, and > 90% of people are using it for the wrong reasons.
TFA should be nominated for a Useless Use of Cat Award [0], particularly since the dissected command apparently "showed the power of true Unix mastery".<p>[0] <a href="http://partmaps.org/era/unix/award.html" rel="nofollow">http://partmaps.org/era/unix/award.html</a>