Prototyping -- and the code generated for that purpose -- needs to be distinguished from production-quality processes and deployment artifacts. This distinctio

Prototyping -- and the code generated for that purpose -- needs to be distinguished from production-quality processes and deployment artifacts. This distinction (which is blindingly obvious to experienced engineers and product owners) is blurred or elided by most of the no-code / low-code sales and marketing materials I've seen. Your example of dynamic charting for data tables is useful; analyzing the performance characteristics and featuresets of enterprise-grade datagrid solutions (eg Ag-Grid, Bryntum) the chasm between a shallow one-off prototype and a properly-extensible and maintainable solution becomes more evident. Ignoring or attempting to bridge that gap with insufficient diligence leads to catastrophe. TLDR I think some of the hostility towards low/no-code tools is less "it's going to take my job" and more "it's going to make a royal mess of things in the hands of people who don't understand".