Anon_Admirer

While the original ISO standard may still have its use cases, your argument involves survivorship bias - just because a technology has been around a while doesn't make it superior. Your false belief that its long life in a group of other standards - is rather a coincidence that is in correlation to its long life and not a cause of it.

Had the USB stick and related softwares for formatting been around sooner .img may have easily won the battle between standards. Unfortunately, CD-ROM was released 1985 and USB flash drives only started really showing up in the early 2000s. We have no way of knowing the counterfactual.

Hope this one gets captured by quackernews - can’t wait to see its description.

Have a look into Power BI developer mode which works with GIT:

https://powerbi.microsoft.com/en-us/blog/deep-dive-into-powe...

They recently released an update in preview that has a more human readable format:

https://powerbi.microsoft.com/en-us/blog/tmdl-in-power-bi-de...

For comparing semantic models there is ALM Toolkit: http://alm-toolkit.com/

You can also edit BI Models with Tabular Editor which can save objects to storage:

https://tabulareditor.com/downloads

And phi-tools for DevOps: https://pbi.tools/ I’d wait in pbi-tools to start working with Power Bi Developer Mode / Power BI Project files

> Wow, you really love PoweBI huh.

Wouldn’t say love but prefer over the alternatives. I still find the user interfaces could have been designed better if they were not so focused on matching like other office products. I wish it was as nice as it is to wireframe in Figma. The ribbon and other office elements are dated and not as conducive to todays standard where good collaboration tools is helpful to bringing developers and designers together while being efficient.

> The versioning is quite bad.

Agreed, but it’s got better over the years. Especially in the most recent release of Power BI projects. I feel that Microsoft’s strategy is to provide this new format and let independent developers create versioning tools while they take on higher priorities. They have often taken things those developers have created and incorporated them into their products. As with all the product requests, you got to pick your battles - I don’t defend which ones they choose. I’m just happy to finally have GIT versioning.

> DAX is pretty; but when it’s big, it’s spaghetti. Worse than SQL.

I agree 100%. I liked how Tableau had a more SQL feeling syntax. I luckily come from an Excel heavy background so adopting was easier than some. I find that most of the verbose code is due to dealing with row and filter contexts which in DAX can be frustrating. Debugging is difficult… I can go on. With that said, others have offering differing opinions (see: https://www.sqlbi.com/blog/alberto/2020/06/20/7-reasons-dax-...). All I can say is that I feel there is probably could have been a better syntax / functional language then the one created to produce the same functionality and maintain independence.

There seems to be a lot of shade here at Power BI. Forgetting Microsoft’s dominance in the market, I’ve much appreciated Microsoft’s approach to data visualization which is soft on the visuals, but gradually improving them and hard on the programming aspects, such as Power Query or “M” and Data Analysis Expressions (“DAX”). The former they have opened to anyone to create via Power BI visuals SDK.

The reason I say this is because something that would take me hours to do in Tableau maybe only take a few minutes with Power BI’s mashup language (Power Query) and the Functional Language DAX. The ability to create temporary tables on the fly and utilize variables and the hundreds of other things you can do with DAX to create complex measures, calculated columns, etc. feels empowering. Most people I’ve spoken to who’ve gone away from Tableau to Power BI and used it long enough start to really appreciate it for the vast capabilities.

Additionally, the latest Power BI visual calculations feature released has made the learning curve a lot shorter for those newer to DAX and all our lives much easier.

On the visuals side there has been a lot of entrepreneurship to create custom visuals with the SDK to do a lot of visuals that just weren’t available in Tableau. So many that I have a hard time going back to Tableau because its missing a visual I need.

Lastly, not many talk about the fact the IT loves it in that its got so many capabilities for providing data governance and security through its various features.

Update and one final thought: there is some genius to me in how Microsoft seemed to have created an abstraction that allows the platform to grow independently and greatly on so many fronts - DAX with new functions and features, the Power BI Visuals and their SDK to do more and keep in with user interface changes, and their BI model approach (which now allows GIT versioning with readability changes).

I don’t think the op meant that in the literal sense of the word “forced”. I took it to mean that arguments were used as a scare tactic to get you to take the multi-vitamin. I don’t think anyone can force people to take anything, but some doctors might be upset after seeing test results if some vitamin levels are low.

There maybe survivorship bias in this persons feelings and beliefs.

The auto-generated SQL from Microsoft's DAX Language for Analysis Services and PowerBi is not bad. I think it comes down to how well developed the expression engine converts to SQL. Microsoft though has had many years fine tuning their expression engine (Vertipaq). It may take a while to develop a competant engine.

I am getting Data Analysis Expressions ("DAX") vibes. Feels like what it tries to do is similar to the DAX language used by PowerBi and Analysis Services for Direct Query but expressed differently I am honestly having a hard time reading their examples versus DAX. Something missing that DAX has is a selected values feature. I imagine looker might have something similar?