I work with something like this on a day-to-day basis. We make and production API endpoints on microservives using a largely click, drag, and fillout options style UI, using a functional language of thiers to transform data, this is all written to XML which is consumed by their engine to create a Java application that deploys into their cloud environment. We can also add custom written Java to fill in a few gaps here and there.

It’s good for what it does, making creating API and consuming a variety of data easy. It does allow us to get down to business and start working with the design of the endpoints and manipulating the data off the bat. It’s only good at that though, it wouldn’t be any good at doing ML or creating an OS or writing a web browser Even with the stuff it’s good at, you can feel the limitations as soon as any real logic complexity is involved and it starts to cumbersome quickly.

And I think that’s where those kind of “languages” will excel, it does this one thing that’s tedious with a lot of nittygritty boilerplate under the hood but that’s not too hard logic-wise well but that’s probably about it.