Laravel 5 released

Post by radlad » Wed, Feb 04, 2015, 8:29 PM UTC

raziel2p wrote: post #73

fideloper wrote: post #62

Earlier quoted context omitted.

FUD. The "architecture" change is the bootstrap repository, which has a new folder structure. I know, scary stuff! Folders! The "architecture" has some enhancements to middleware and fleshing out events/commands to a "command bus". Basically, you get more sugar on top of the (mostly) same architecture. Whoops caused a lot of headaches behind the scenes, and did stupid things like convert ALL http error responses to 5…

That's a shitty explanation for dropping Whoops. The first time I remember the discussion of it being dropped got brought up was because of a bug in the framework relating to the assets, where Taylor didn't hesitate to blame Whoops and deleted comments on Github pointing out that the problem was actually in his own code. It would've been super easy to add some code that sets the HTTP code for Whoops's response if tha…

Post by porker » Wed, Feb 04, 2015, 8:56 PM UTC

_broody wrote: post #64

tomcorrigan wrote: post #30

Earlier quoted context omitted.

Extending the IoC container?? A ControllerFactory?? You never do anything like that in Symfony. The thing I appreciate most about Symfony2 is how it enforces good design patterns.

One might argue that the SOLID principles applied in Symphony and inherited by Laravel are in fact anti-patterns which only serve to add massive cognitive overhead. They've wrecked countless Java projects over the years and are now going to do PHP the same favor. There's even less reason for a scripting language with a GIL to be saddled with this level of complexity, than there is for Java.

Post by josegonzalez » Wed, Feb 04, 2015, 9:52 PM UTC

debacle wrote: post #99

josegonzalez wrote: post #87

Earlier quoted context omitted.

As a Core developer of CakePHP, I'll tell you that the community at large loves major releases more than they like stability. Something about using the newest toy really gets a lot of people going. We actually have had quite a few developers tell us our framework is dead, despite ongoing development on a new major release and monthly minor/patch releases for the current stable line for 3+ years. I can't comment on La…

The vocal community is likely in the realm of 5-10% of the actual active userbase. You should cater to most of your users, not just the bored ones. Your framework is dead because you've continued to prove that you don't understand what PHP 5.3+ is and means. I say that as someone who has been forced to use CakePHP for ~10 years. You've always lagged far behind in the concepts that other frameworks have down pat.

Post by aikah » Thu, Feb 05, 2015, 12:07 AM UTC

JonoBB wrote: post #88

debaserab2 wrote: post #84

Deal-breakers for me with Laravel: - Blade templating language. I don't need yet another templating syntax to learn, especially one that isn't analogous to others I know and are common among other frameworks. - I really can't imagine going back to an active record based ORM. I've learned too many hard performance lessons from Doctrine1 and rails at this point. - Facade/proxy pattern based classes. I think as they are…

Those don't have to be deal-breakers. - You don't have to use Blade. Use Twig or Smarty or whatever you want - You don't have to use Eloquent. Use raw queries or Doctrine or whatever you want - You don't have to use Facades - use the IOC container to get whatever you want Its so easy to plug-and-play with composer, and there are so many other features to laravel.

Post by vatotemking » Thu, Feb 05, 2015, 5:19 AM UTC