Nocode is not something new. It was there and it will continue to evolve. It's just that recently, we started using Nocode in many areas which we didn't consider before.
Perhaps the answer is no-code with an 'eject' function, that spits out actual code that you can then build on once you have exhausted the possibility of no-code.
Or, going in the other direction - using code to build the building blocks, which you can stitch together with no-code. Some libraries already do this, such as Elsa Workflows.
The problem with some of the no-code platforms that allow you to write code, is that the code is still within their framework, and you can't use the language's package ecosystem. The platforms that solve this will make the code-in-nocode function exponentially more powerful.
It will. Once no-code goes from an alternative to coding, to its sidekick. Firebase is a lowcode version of node+mongo, they got it almost right and it exploded.
9 comments
[ 2.9 ms ] story [ 37.1 ms ] threadMaybe an ideal no-code platform would be a UX innovation on some DSL.
Or, going in the other direction - using code to build the building blocks, which you can stitch together with no-code. Some libraries already do this, such as Elsa Workflows.
The problem with some of the no-code platforms that allow you to write code, is that the code is still within their framework, and you can't use the language's package ecosystem. The platforms that solve this will make the code-in-nocode function exponentially more powerful.
Using the package ecosystem brings with it a can of worms that if not handle right could doom the system. I'm talking security ofc.