cwebber@social.coop ("Christine Lemmer-Webber") wrote:
It was less than a week ago that @dthompson and I were discussing what to do about the accountant needing some very specific data and that it was going to be a huge headache to pull out what we needed, and that adapting anyone else's code with the Beancount stuff wasn't going to be trivial.
I off-hand'edly said "Well I did that Beancount to JSON exporter, I mean I *could* just write our own tools to go over it, but that seems absurd. I should probably just spend a few days trying to get all the individual pieces of information through Beancount, but it's so painful because the APIs are undocumented and I'd have to work with some imperative APIs."
Dave: "Sounds like you should just process it in Scheme, it'll be less painful."
Which is what I wanted to do, but it seemed unlikely it could be a time-efficient choice.
But it ended up being *incredibly* time efficient! I can't imagine such success so quickly in anything other than a lisp'y language, for all the "Lisp is Clay" reasons.