I think main difference is how PRQL translates into query execution plan, with SQL you need to read entirety of query to get rough understanding of order of ope

I think main difference is how PRQL translates into query execution plan, with SQL you need to read entirety of query to get rough understanding of order of operations (especially if you join two-three tables and have some nested and lateral queries). with PRQL I see that the order will be explicit and set up by developer, so any footguns will be evident. things like predicate push down, optimization fence, variable rewrite, etc are not needed to be relied upon, because pipeline of query is more explicit in PRQL also since it is new lang, it can be naturally extended into ETL type data pipelines also because PRQL can be translated into query execution plan - it can be converted into non-SQL languages like MongoDB or pandas / spark / etc, eliminating SQL altogether for distributed nosql engines