It is the first critique of functional programming I've read from someone who clearly knows their shit.
I plan to look at miniKanren more when I get the chance.
I done a fair amount of math though likely less than the author but I have a similar impression - the things that are hardest to understand aren't necessarily the best tool for every job, despite their beauty. And beautiful abstraction for its sake can be a dangerous anti-pattern as much as excess hacks and simplicity.