3 ms·
For those of you finding it hard to read the paranthesis-heavy text, the very last part struck a chord: "If I have to write one more polyglot bash / awk / pyth
by defdac 17y ago
For those of you finding it hard to read the paranthesis-heavy text, the very last part struck a chord:
"If I have to write one more polyglot bash / awk / python script to gather data from log files on a bunch of different machines, demux that into a time-ordered event stream, pipe it through something to munge it into some slightly different format, ship that off via post to some web address and get some JSON back, parse that into some other shit, do some computation over it like aggregation or date math over time stamps with unlike representations, wrap the results up in an HTML table and send that table in a MIME-enabled e-mail to myself I think I am going to explode."
- berntb 17y agoCPAN is afaik the gold standard to make that kind of thing bearable. It isn't really a language thing. (Since everything seems to go to Moose (a backport of most of the Perl 6 OO model) in the Perl world, there might be an impedance mismatch in a few years with old style libraries and new?)
- Diederich 17y agoMoose and standard/old style libraries are entirely and transparently inter-operable.
- berntb 17y agoYeah, but I was thinking more brain mismatch. On the other hand, most CPAN libraries aren't so large that they use APIs which needs to be overridden; I was probably wrong. (Anyway, it was irrelevant to my point. :-)