Hey all, finally released a pretty cool (well I think so) demo of the rules language DSL we built for fighting spam/abuse/fraud/all-the-bad-stuff at Smyte (acquired by Twitter). It's heavily SQL-based but includes a lot of features for working with very large teams, deploying new rules in seconds, and tracing which rules caused an action to occur. Demo: https://websqrl.vercel.app/twitter Docs: https://sqrl-lang.github.io/sqrl/ Motivation: https://sqrl-lang.github.io/sqrl/motivation.html Would welcome any comments/questions. Just glad to finally get this out the door 🥳

Is there an order of execution for the rules, or do they all apply simultaneously? And what happens if you specify cyclical rules?

@Jason Morris there's a cycle detector so cyclical rules will be caught at compile time they all are applied simulataneously, but there are some automatically generated features to help with waiting (such as

SqrlExecutionComplete

that depends on all of the rules finishing executintg)

I'm curious how you came to the conclusion that avoiding the halting problem was worth eliminating loops and recursion. In practice, were there a lot of situations in which it caused bugs that weren't caught in testing, or easily avoided?