Great article. To circle back to the point, some of these visualisations also contain hints to how they could be used for actual programming. E.g. changing arr

Great article. To circle back to the point, some of these visualisations also contain hints to how they could be used for actual programming. E.g. changing arrow type in the ownership diagram is a good example of a change that is very annoying to do manually in Rust but it's trivial in the diagram. The challenge is to connect this action to the whole programming workflow, which is currently optimized for text, I'd even say overfitted. Rust especially is famously difficult to process by tools. I think we might need to use a language that is specifically designed to be processed by visual tools to make it all work.