As you mention, there was quite a lot of this in the 1990s, and there are still lots of tools that employ this kind of workflow- django, for instance- for the a

As you mention, there was quite a lot of this in the 1990s, and there are still lots of tools that employ this kind of workflow- django, for instance- for the admin side of the UI. These approaches are no good for anything user facing- design and UX is too important. The larger issue is that no system is an island, from a data perspective, and most work is brown, not green field. Subscribers and policies already live in the system the company has been using for 20 years- well, likely in a dozen systems that the business has acquired from competitors and continues to operate while struggling with data integration. Meanwhile marketing and sales has been using multiple generations of SAAS tools, finance has their own on prem or SAAS tools- all of which need to work with a common set of entities but which have different opinions about exactly how those entities are shaped. This is the reason data lakes and SAAS ETLs are so important right now. Static/dynamic generators don't solve a painpoint at this point. It's not about new systems/data, it's about existing systems and data. HTH.