I tend to use Laravel when the client/project forces me to use PHP rather than Rails. It's not bad when coming from the Rails world.
I also have a bit of pride that it's made in Arkansas. Yes, we have computers and the internet here.
Laravel 5 released
51–60 of 114 posts
Re: Laravel 5 released
#52Earlier quoted context omitted.
A lot of the over engineering in Laravel comes from Symphony, which in turn inspires how Laravel is built. And with the Proxy pattern in use everywhere, it inspires high coupling in your code in a way that doesn't quite look like coupling but is nonetheless.
I would argue that Symfony is well engineered, not over engineered. The fact that Laravel is already at version 5 demonstrates just how poorly engineered it was in the first place.
Did you just go full retard?
Re: Laravel 5 released
#53After using Laravel 4 for an internal company tool I have a hard time recommending it (sadly, I was hopeful). I found the docs to be uneven in quality/scope, some key features (mostly around the ORM) missing and the 'feel' to be slightly off. It's hard to quantify, but I have used CakePHP, Yii, Rails (0.9 through 4), Django and plenty of home-grown 'frameworks'. From all those the most cohesive and understandable to…
Maybe it's a matter of taste?
I have worked with Symfony2, Zend Framework, Yii, Kohana and Laravel and find Laravel the most intuitive to work with.
I like that you can start using it for very rapid prototyping and refactor into more complicated structures as the application grows.
Re: Laravel 5 released
#54After using Laravel 4 for an internal company tool I have a hard time recommending it (sadly, I was hopeful). I found the docs to be uneven in quality/scope, some key features (mostly around the ORM) missing and the 'feel' to be slightly off. It's hard to quantify, but I have used CakePHP, Yii, Rails (0.9 through 4), Django and plenty of home-grown 'frameworks'. From all those the most cohesive and understandable to…
It strikes me as a project that should've been an internal framework, not a public one. Too many things break and change constantly. Rapid release cycles is a good thing for smaller libraries with specific tasks, but I expect a framework to remain largely unchanged (except bugfixes, of course) for longer periods of time.
Unless Taylor gives away control of the project, I don't see it happening. It'll keep being a popular framework, though.
Re: Laravel 5 released
#55Laravel represents what modern PHP can do and be. Clean, organised, fully object-oriented. Kudos to what Taylor Otwell has created both from a marketing perspective and technical standpoint.
> Laravel represents what modern PHP can do and be. Clean, organised, fully object-oriented. In a JavaEE circa 2003-5 way. Not exactly what modern programming is about...
We got it the first time https://news.ycombinator.com/item?id=8997114
Re: Laravel 5 released
#56Laravel represents what modern PHP can do and be. Clean, organised, fully object-oriented. Kudos to what Taylor Otwell has created both from a marketing perspective and technical standpoint.
I was a little scared by the heavy use of static method calls in Laravel 4. L5 has made the statics easier to ignore if that is not your thing. But after understanding the Facade pattern that is widely used by the framework, I've concluded that the use of the static method calls is not an antipattern at all.
It really is less of an antipattern in PHP than other languages. With every request being its own process you don't have to worry about singletons as much, and as long as it's easy to swap with mocks/fakes/whatever it's all good.
Re: Laravel 5 released
#57If you're new to Laravel or want to learn more check out http://Laracasts.com . Jeff Way does a great job. (Just a fan/current subscriber).
Jeffrey Way is the best. Back at Tuts+ I'd only watch his courses—no one else was as good of a teacher as him. Laracasts is even better.
His 30 days to learn jQuery was a critical growing tool for me - if you're at all interested in low-level front end JS, definitely check it out. Its free.
Re: Laravel 5 released
#58Having watched Laravel 5 throughout development, I'm personally unhappy with the fact that most of the nice features of Laravel have been removed.
For example, the default version of Laravel 4.x shipped with the "Whoops" PHP stack trace view, which is far superior to the L5-default Symfony stack trace view. Other features were removed too, including the HTML library. Blade tags were changed for no reason.
Overall, it feels like instead of adding requested features, Taylor decided to redesign the architecture for no reason.
Re: Laravel 5 released
#59Earlier quoted context omitted.
Having worked with Kohana, CodeIgniter and WP, Laravel is the reason I started writing PHP again. Also being a node developer, Laravel feels at home with Express(both influenced by Sinatra). Artisan command line utility, Migrations for DB version control, Blade template engine and the neat directory structure are some of the things I like apart from the community ofcourse
What is the thing you don't like about Laravel community? (or is this what you say when other PHP devs are involved?)
I think that he actually likes the community. The wording might be quite confusing but I think that's what he meant.
Re: Laravel 5 released
#60Having watched Laravel 5 throughout development, I'm personally unhappy with the fact that most of the nice features of Laravel have been removed. For example, the default version of Laravel 4.x shipped with the "Whoops" PHP stack trace view, which is far superior to the L5-default Symfony stack trace view. Other features were removed too, including the HTML library. Blade tags were changed for no reason. Overall, it…
The single maintainer just didn't want to maintain them, which goes to show how Laravel really just is his personal project that got really popular, not a community-driven effort.