4 ms·
NoCode isn't dying. But it has problems
- deleted 5y ago[deleted]
- MathMonkeyMan 5y agoI suspect no-code platforms are high level languages that don't assume deference to the styles of existing programming languages. Maybe an ideal no-code platform would be a UX innovation on some DSL.
- anandnair 5y agoNocode 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.
- llimos 5y agoPerhaps 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.
- jaisondavis 5y agoI'm building the latter. A platform that allows you to use code when you hit limits with the visual builder. 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.
- aaaaaaaaata 5y agoWhy do you need them after you have your code?
- mbrodersen 5y agoNoCode has been around for a very long time. It works OK in some specialised areas. But it can’t compete with the power of real programming languages.
- jaisondavis 5y agoIt 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.
- mbrodersen 5y agoYou still program in Firebase? Excel is probably a better example of a super successful no-code application.