3 ms·

I'm seeing a lot of love for Laravel 4 at the moment and I'm not 'getting' it. Sure, the framework's easier to pick up than Symfony2 and not as over-engineered,

by porker 13y ago

I'm seeing a lot of love for Laravel 4 at the moment and I'm not 'getting' it. Sure, the framework's easier to pick up than Symfony2 and not as over-engineered, but it doesn't feel as complete (forms, anyone?) or as well designed (what's up with all these static methods?) Laravel 4 is becoming the CodeIgniter of the PHP 5.4 frameworks - simple enough for people to jump on as they can get something done. And the CodeIgniter comparison is not a compliment.

ceejayoz 13y ago
> what's up with all these static methods? http://laravel.com/docs/facades http://laravel.com/docs/facades
pearjuice 13y ago
Laravel doesn't come close to CI in terms of trash. It is very well architectured to the point where everything is modular, testable, properly documented and done with a reason. Static methods are actually facades as pointed out and are key in having proper testable applications. * Forms? It has support for forms in more way than one. Read the docs! :-)
- porker 13y ago
  > Static methods are actually facades as pointed out and are key in having proper testable applications. Thanks, I had a look about a year ago at the facades document and it seemed a justification for using static methods, rather than a reason. I'm pushing hard on this as I really want to understand it. I am surrounded by PHP programmers chanting "Every time you use a Singletons a kitten dies" and "No static methods". Yet when I used (and contributed to PEAR) they were positively encouraged. Is the change another fad, or fact-based? > * Forms? It has support for forms in more way than one. Read the docs! :-) I have :) I see helpers to generate form fields and a validation library. I see no way to create form entities, to extend forms (to create variations on a base form), or to abstract the field definitions from the view (while the visible value of select box options could be in the remit of the designer, modifying the value shouldn't be accessible to anyone other than the programmer, and neither IMO should choosing the field type (drop down or multiple radio buttons? Multiple select or checkboxes?) Also no support for 0..N repeating fields baked in (with conditional validation), or 1..N fields - stuff I use in almost every form. Every form library I've discovered falls short in these requirements though!

by porker 13y ago

ceejayoz 13y ago

> what's up with all these static methods? http://laravel.com/docs/facades http://laravel.com/docs/facades

pearjuice 13y ago

Laravel doesn't come close to CI in terms of trash. It is very well architectured to the point where everything is modular, testable, properly documented and done with a reason. Static methods are actually facades as pointed out and are key in having proper testable applications. * Forms? It has support for forms in more way than one. Read the docs! :-)

porker 13y ago
> Static methods are actually facades as pointed out and are key in having proper testable applications. Thanks, I had a look about a year ago at the facades document and it seemed a justification for using static methods, rather than a reason. I'm pushing hard on this as I really want to understand it. I am surrounded by PHP programmers chanting "Every time you use a Singletons a kitten dies" and "No static methods". Yet when I used (and contributed to PEAR) they were positively encouraged. Is the change another fad, or fact-based? > * Forms? It has support for forms in more way than one. Read the docs! :-) I have :) I see helpers to generate form fields and a validation library. I see no way to create form entities, to extend forms (to create variations on a base form), or to abstract the field definitions from the view (while the visible value of select box options could be in the remit of the designer, modifying the value shouldn't be accessible to anyone other than the programmer, and neither IMO should choosing the field type (drop down or multiple radio buttons? Multiple select or checkboxes?) Also no support for 0..N repeating fields baked in (with conditional validation), or 1..N fields - stuff I use in almost every form. Every form library I've discovered falls short in these requirements though!