Low code isn't inherently that bad as long as it offers a way to integrate with traditional code. Microsoft Excel is tremendously succesful in this area.
Low code isn't bad until you try to use a lot of it just like OOP isn't bad until you use too much of it. There is always a temptation that leads one to use too much of these. We have had low-code visual software design for decades. SQL Server Integration Services comes to mind. It does not solve the core problem. Maintainability. The last thing software needs is an invitation to more people that aren't yet aware of the problems of maintenance.
There is not an extremely high barrier to coding. That is not a problem. There is a huge barrier to learning how to produce maintainable and adaptive systems and that barrier is only made worse with low-code tools and services.
I worked with adding some functionality to a Microsoft PowerApp Covid office tracker template. Having to navigate the GUI for everything was quite cumbersome.
Although it was only two function calls in two places, it seems that every time the template is updated, the calls will have to be added back. Instead of doing a merge in Git, you will now have to remember all the navigation steps to add the changes each time. I don't want to think about what happens if you have more than one person working on an app.
There is not an extremely high barrier to coding. That is not a problem. There is a huge barrier to learning how to produce maintainable and adaptive systems and that barrier is only made worse with low-code tools and services.