Ah, nice to see a mention of M. I don't see it mentioned a lot on HN and get the feeling most folks here probably don't even really know about it because it's so embedded in PowerQuery and PowerBI. It's actually not a bad language, it's just quite verbose in terms of the keywords.
I actually draw on my experience with M a lot in terms of the input that I give to PRQL because for data munging M is quite a good language.
Until we did the [] to {} syntax swap in 0.9, PRQL actually started to look a lot like M because M is the only other language I know that has [] for tuples.
What holds it back most of all I feel is the prison that is the Power Query editor (I have a sizable list of small and large papercuts in mind).
Now that PBI allows experimental export to pbip, change may be on the horizon. Hoping for more fine-grained tools, a better profiler and a better editor.
Will look at PRQL when I find the time. The planned column lineage feature and type checking e.g. seem like a godsend. Good work!
I actually draw on my experience with M a lot in terms of the input that I give to PRQL because for data munging M is quite a good language.
Until we did the [] to {} syntax swap in 0.9, PRQL actually started to look a lot like M because M is the only other language I know that has [] for tuples.
(Disclaimer: PRQL contributor here)