The reason this doesn't work the way the author wishes: > The idea of co-designing language and UI Is because commingling presentation, use cases, and biz log

The reason this doesn't work the way the author wishes: > The idea of co-designing language and UI Is because commingling presentation, use cases, and biz logic is highly coupled. UNIX files have just open, close, read, write, and seek in the simplest form. The UNIX 'everything is a file' is really just a form of dependency inversion. I am old enough to remember when the visual languages and UML were supposed to replace programmers with architects with GUIs. But it ignored that commingling implementation details produced systems that are tightly coupled with implementation details and is difficult to work with. It seems that these principles are ignored and rediscovered over and over again. Clean, hexagonal, onion, and ports and adapters architectures being some of the most recent versions. The UI should depend on the core system and that core should be ignorant of the UI as much as possible. Adobe has no real reason to expose PS functions that way, and obviously I am talking about ideals. But it is just simple reality that when you tightly couple to implementation details you paint yourself into a corner.