[Yes2020]

My experience with " no code" reinforces the issues raised in ex other comments, with a little emphasis to add:

If you never learned your times tables, then used a calculator, imbedded calculation loops are tricky to troubleshoot .

" no code" layers this more deeply, creating a very large number of programming code lines, function calls and subroutines on interpreted code that runs slow anyway. It can be difficult to untangle when things just don't work right.

Interpreted code always runs slower that code compiled into machine code. Maybe adding in AI and machine learning will eventually be able to take this first-rev , " no code " prototyping and optimize it into an efficient, effective, fast system that is bullet proof, and intellectually protected.

[verdverm]

Not all low code platforms use interpretation or dynamic code creation. I work on one which is language agnostic / polyglot (see other comment here) and have seen more examples from other devs / competitor demos. You can think of this probably more like code gen for stubs, but one place to write in Cue and multiple tech / language outputs (for our Hof tool).

You are right about the complexity hiding and difficulty therein. It's part of the reason ours is open source.