I was wondering the same, why not SQL? > This leads to a lot of logical conditions, since to prevent double-counting each aggregate tuple’s conditions must ass

I was wondering the same, why not SQL? > This leads to a lot of logical conditions, since to prevent double-counting each aggregate tuple’s conditions must assert both that the matching tuples matched and that the non-matching tuples didn’t. I understand and know to handle edge cases with SQL, I'd have to learn that all over again with a custom language and its own unique quirks. If I was putting such an investment, I'd want it to be better established. Unless of course it's to scratch an itch and this is a perfect way to start out and share. Nice work and good luck.