WYSIWYG fails for two reasons: - Programming errors most of the time break everything. You probably know how bitchy Word can be. Errors will be frequent und fi

WYSIWYG fails for two reasons: - Programming errors most of the time break everything. You probably know how bitchy Word can be. Errors will be frequent und finding them when you don't really know what happens under the hood will be very difficult. - WYSIWYG does not abstract very well. The big power of programming however is, that you can build your own tools from a minimal set of building blocks. Visual representation for self-build tools and routines will not be pretty out of the box. --- Those visual languages that do have a big userbase do the following: - no WYSIWYG, just "nodes". The visual parts of the nodes: - - inputs and outputs are often connected with "wires" - - simple control UI like a knob or a button can be shown directly - they allow wrapping a bunch of wired mess in to a box with simple in- and outputs again - some allow to jump back in to code where necessary - in general nice for small art-projects - difficult or at least in-flexible for complex stuff - often a lot more copy+pasting ---