Comment by Gergely Polonkai on "Wappler = The beginning of the end of coding?" | Hashnode

Gergely Polonkai

You have to believe in things that are not true. How else would they become?

Oct 19, 2018

Let’s assume for a moment that Jason Knight is wrong (most probably he’s not) and this… service can create an awesome app for you. Do you know what this awesome app will still miss?

Business logic.

No matter how awesome such a tool might be it won’t be able to model your business logic for you. Thus, the generated awesome app is nothing but a framework, of which we already have enough out there. Or something we call a boilerplate; of which we also have tons out there.

I wouldn’t say i don’t use such frameworks or boilerplate generators every now and then; it takes off a huge load of typing from my fingers, but there’s a reason no truly big apps use them. At the end you will strip them down so much it won’t be a framework anymore, but a specialised piece of code written for your own business logic, by your own programmers.

Brian English

Wappler Ambassador

Oct 26, 2018

I am guessing you have not used this tool and base your comments on supposition. I do think that the product can sometimes be mis-represented by the idea of a visual programming tool as this will cunjure up ideas of services like Wix. Wappler is more a visually managed web app language where business flows can be and are catered for. You still need a an understanding of coding, particularly JavaScript to get the most of it but that is part of it's beauty, new developers can hone their skills on the basic visual flows where more experienced developers can add custom code to the modules to extend them. Nothing will ever remove the need to code 100% but Wappler can do a huge amount of the heavy lifting and make a developer far more productive.

The irony is that experienced developers will not even bother using something like Wappler. They will just code, and at least competent ones would curse at anything that a GUI software like this generates.

I found that the best way to become more productive in web development was to stop avoiding hard work of learning and practicing, master the core technologies first and foremost, figure out how I could write less code to begin with, and avoid a thick abstraction layer that has the issue of leaky abstraction and adds a whole set of troubleshooting work.

Search Hashnode