In Defence of Visual Scripting

As far as I'm aware, visual scripting runs into one of two unavoidable problems:

1) Either it is very limited in scope. This is probably most of the times where it can be applicable, but that also makes it unsuitable for building anything complicated. In times like 3d material builders (IMO where visual scripting shines) this can be an extremely powerful and useful feature. But in times like say, game programming, I think it leads people down the garden path because oftentimes where it's not super limited scope it runs into...

2) Greater complexity than just learning to code. In both, you need to formulate logic, but usually visual scripting languages that are genuinely powerful cannot be abstracted sufficiently or you run into 1. This monolith then grows and grows until you end up with something like Construct 3 which is super complicated. The time used to learn how to do things in it would be better used learning how to do things in a traditional scripting language. You also lose all of the benefits of visual scripting - the timesave.