I'm eager to try out Enso. > why visual languages have not thrived In my experience, "visual" gets you ~90% to done. But inevitably, you have to drop to code.

I'm eager to try out Enso. > why visual languages have not thrived In my experience, "visual" gets you ~90% to done. But inevitably, you have to drop to code. To handle the use cases and edge cases not anticipated by the framework. And then you're fighting the framework. Which is a 800lb angry gorilla sitting between you and your goal. For flowchart & block style programming, the pitfall is the error handling. For patch cord style programming, the pitfall is conditional behavior and any data flows which are not 1:1 input-to-output. (Non-1:1 use cases are a challenge for all ontology/taxonomy systems, more generally.)