> But here's the problem: at some point, the user wants the tool to do something beyond what the tool can do. > And at that point, the user is stuck. Customer

> But here's the problem: at some point, the user wants the tool to do something beyond what the tool can do. > And at that point, the user is stuck. Customer service recommends posting a feature request in the product forums and all the user can do is wait... and hope something gets implemented that solves their problem, or find a new tool. Is this not the problem with any programming language? It's turing-complete, yet you find something you can't do (I mean, brainfuck is turing-complete, but try implementing a closure in it), you complain to the maintainers, they say it doesn't fit the design criteria. Sure, you might be more likely to fit those limits earlier in a visual code design tool, but that's not a fundamental design limitation, just an implementation one.