Hm... it reminds me of Django or other object oriented type programming languages where readability has been reduced to a minimum so that people can do things in "one line of code".
While elegant looking... it's very hard to read, unless you know by heart the parameters of the built in functions.
I much prefer a good, structured query language statement which is easily readable by any one coming across it (including myself) even years and years later... because each clause of the statement is going to have the same purpose/function no matter what, is called out by name (select, from, where, order by, group by etc).
While object oriented code is more elegant at first glance, and people can brag about how they were able to build an interface in 15 minutes with a few choice, built in objects and functions... my concern is that in 15 years people will look at that code and be unable to read it.
I would put this DAX language and syntax there as well... in the elegant but eventually undecipherable category.
That's my rant in any case.