Wappler vs Laravel

[nexgen]

I’m currently evaluating wappler and was wondering how wappler compares with laravel.

I’m curious about:

• How wappler helped speed up the development?
• What are the challenges you could have solved in laravel but not able to do that in wappler?
• What challenges are solved by Wappler that you can’t do in Laravel?

[brad]

@nexgen

How wappler helped speed up the development?

The smart UI gives you everything you need at the click of a mouse. Very seldomm do you ever have to go into the code.

@nexgen

What are the challenges you could have solved in laravel but not able to do that in wappler?

Laravel is limited to PHP. Also, that question is asked kind of backwards for this group. You should be asking what challenges are solved by Wappler that you can't do in Laravel. Laravel also cannot build mobile apps.

[nexgen]

@brad

Also, that question is asked kind of backwards for this group. You should be asking what challenges are solved by Wappler that you can’t do in Laravel. Laravel also cannot build mobile apps.

Nice suggestion. I have added that question in my post.

[Apple]

@nexgen

How wappler helped speed up the development?

No more php artisan make:migration

@nexgen

What are the challenges you could have solved in laravel but not able to do that in wappler?

Server-side rendering is not a 1st class citizen on Wappler, template variables and such are generally processed client-side after an API ("Server Connect") call instead of being rendered server-side

@nexgen

What challenges are solved by Wappler that you can’t do in Laravel?

One tool to develop both the front-end and back-end, no more fussing around between tools or developing the front-end exclusively with a code editor

Edit: For a more comparable experience to Laravel, use NodeJS. The PHP version of Wappler is like old-school PHP, not Laravel-style with templates and such

[nexgen]

@Apple

Edit: For a more comparable experience to Laravel, use NodeJS. The PHP version of Wappler is like old-school PHP, not Laravel-style with templates and such

Is NodeJS is the way to go for the wappler projects? I’m wondering why layouts/partials are not available for PHP.

[Apple]

Well, I came direct from Laravel to Wappler NodeJS, never really experimented with Wappler’s PHP. You’ll find lots of people using either server target.

The most prominent case is of the user mozzi, he went from PHP to NodeJS and then back to PHP (he talked about it in a topic).

The PHP server target came before NodeJS, perhaps at the time templates weren’t considered. They introduced it in the NodeJS server target, and they can’t introduce them in PHP in order to not break compatibility with old websites already developed with Wappler.

Btw templates are limited to one level of depth, you can’t do fancy inheritance like you can with Blade, but you still have master layouts/templates and partials

[nexgen]

@Apple

The most prominent case is of the user mozzi, he went from PHP to NodeJS and then back to PHP (he talked about it in a topic).

I read the mozzi’s thread and it is now making me confused. Should I choose node or PHP. I had settled with the Node but reading about hosting issues look like I need to start with PHP.

What’s your suggestion?

[Apple]

Mozzi had limitations due to his location in South Africa - a lack of hosting providers supporting NodeJS for an acceptable price

Unless you have the same concerns, from my point of view you should stick with NodeJS

[nexgen]

@Apple

Unless you have the same concerns, from my point of view you should stick with NodeJS

Thank you for the suggestion.

[psweb]

I am in South Africa too, but use Digital Ocean mainly, but that is because most of my client base is not South African, so I have not really had a similar problem as Mozzi did. I use NodeJS as much as I can.