Why I stopped creating PHP projects with Wappler and why you probably should too

You all know my beef with PHP. I wouldn’t start a PHP project even if your life depended on it. This decision is tool agnostic.

But why did I stop doing it with Wappler specifically?

For each server model they have to support the turnaround for new features, bug fixing, documentation and general support increases. Yes it is all kind of abstracted for us, but they have to build and support such abstraction for each backend and that takes time.

Wappler’s app is built with javascript, html and CSS. That means that they have to be more comfortable with those languages than with any other.

So why not do us a favour by doing them a favour?

The most practical server model we can choose right now is nodejs. By choosing nodejs you are choosing the same stack of tech as they have to use on a daily basis to support Wappler app.

Next time you start a project do yourself a favor and choose nodejs. By doing that the team can shift focus to nodejs and build features at an improved rate.

If I was able to wish one thing is that Wappler 4.0 was reserved exclusively for nodejs and newer server models.

And Wappler 3.x branch was left for older models and only received security updates for some time.

I understand this is a hard choice after so many hours have been poured into php and asp but all things must come to an end if its in the name of progress.

Community Page
Last updated: