4 ms·
The simple answer is that it's too distinct from where we're trying to meet our users. We're not anti-PRQL, but our users (folks in security) coming from Kusto
by caust1c 3y ago
The simple answer is that it's too distinct from where we're trying to meet our users.
We're not anti-PRQL, but our users (folks in security) coming from Kusto, Splunk, SumoLogic, LogScale, and others have expressed that they have a preference for this syntax over PRQL syntax.
I wouldn't be surprised if we end up supporting both and letting folks choose the one they're most happy with using.