That's the same thing with all technology choices though - if requirements change substantially you always risk a rewrite. If write a full-code application with all your logic in server-side .NET and suddenly your users have a requirement to use it offline, and then you are trapped with an app that needs to be rewritten with data that needs to be migrated in order to implement one feature
This is all part of having a good level of intuition for what capabilities you are likely to need, and then picking appropriate technology.
There is a vast difference between the things which are blocked because youre not using a turing complete programming language and things which are blocked because of the nature of that language though.
You'll probably run up against the former quite quickly. The latter possibly never.
Yeah but ‘Turing complete languages’ have their own limitations compared to no code, like being comparatively slow to develop in.
(In quotes because many/most no-code environments are Turing complete, but you still wouldn’t want to develop certain apps/logic in them)
Until you need it to do something slightly beyond its capabilities and then you are trapped with an app that needs to be rewritten with data that needs to be migrated in order to implement one small feature.