3 ms·
No-code tools fail when it comes to leaky abstractions and complex logic. They might solve some trivial cases, but they are not the end of programing.
by gostsamo 5y ago
No-code tools fail when it comes to leaky abstractions and complex logic. They might solve some trivial cases, but they are not the end of programing.
- kandruszkow 5y agoLet's say it's a marketing campaign or a quick project. Do you think it's better to develop the website with code or use a web builder?
- gostsamo 5y agoWhat problem are you solving? If you want to expose already existing data, text, pictures, or do simple transformations, no-code is good. If you need to develop your logic, gather conditionally data from different sources that needs to be parsed and so on, this gets complex and you'd better use a proper language. No-code only means that the code is somewhere else and it has been nicely packaged for easy reuse. The moment you can't build it with lego, you can't do it with no-code. :)
- kandruszkow 5y agoI'm doing research, thus wanting to see what others think of it. I tried to spark conversation to see where/when/who and for what purpose people can use it.. (when is the exact time to switch from no code to for example hiring a developer)
- hobs 5y agoI was talking to a youngin and mentioned that it wasn't exactly the same, but we've seen RAD, Access, FoxPro and other "low code/no code" environments before and it wasn't the end of code; generally as things changed it was harder to maintain these interfaces to actual code and they were commercial offerings that eventually fell apart because corporations don't do much indefinitely.