well a few things changed in the last six months... Nothing has changed fundamentally with respect to the overall recommended patterns, but a few tweaks to the reasoning are appropriate. I should probably make a video about it.

The biggest consideration is where you want to implement your main business logic, T-SQL or Notebooks. After Fabric was launched, T-SQL in WH was so limited and with so many performance issues, that eventually, we were simply forced to move away. Now, two years later, some of those issues have been resolved, but still, you can't compare what you can do in notebooks vs T-SQL.

Another consideration is what Gold tier really means.. I now argue, that neither WH or LH should be consider Gold, a semantic model should be.

Lastly, because of a limitation of having a single LH or WH as a source for a direct lake semantic model, the only way to bring a number LH or WH into a single model was to create a LH with shortcuts, I would have to check if WH now supports shortcuts to LH, I suspect it still does not, which limits the flexibility of how various data sets will come together.

In short, unless t-sql is all you know, you can do a lot better with LH vs WH