I think the key point on this is `some use cases`. For people who've spent a lot of time with ANT, you might be familiar with this article from its creator: ht

I think the key point on this is `some use cases`. For people who've spent a lot of time with ANT, you might be familiar with this article from its creator: https://web.archive.org/web/20041217023752///x180.net/Journal/2004/03/31.html https://web.archive.org/web/20041217023752///x180.net/Journa... It was possible and even made sense to use XML as the format for a build tool, however, it got stretched way to far. The idea was applied in use cases that were less and less appropraite, as a result years later you end up with something that is unwieldy and doesn't make sense and, generally, thought of as "terrible". There are use cases were JsonLogic might make a lot of sense, and for those that is great. Generally, I'm sceptical as there is high risk of increasing couplings in a way that will make change much harder. This will be particularly true if it is applied to use cases that don't truly warrent this kind of solution.