We have been using Laravel for over 8 years. Nothing but praise. It's a framework we could rely on. No painful upgrades and clear documentation. For us it's a pleasure to work with. I also recommend Laracasts from Jeffrey Way.
Laravel 9
21–30 of 262 posts
Re: Laravel 9
#22I like using plain PHP + PDO MySQL. I structure it so almost all files contain a single function/MySQL query, with very little dependencies. I already know how to implement core functionalities when needed (e.g. CSRF, user permissions). Why should I consider Laravel if plain PHP seems to work excellent in my case (been able to maintain the same codebase for over 9 years without issues, can quickly create a new app if…
> Why should I consider Laravel
If you work on all those projects alone, and you're happy doing this, you probably wouldn't. You aren't the target market for a framework like this.
Laravel (and any good framework, really) is for people who want a consistent dev experience _with good documentation_.
Re: Laravel 9
#23[deleted]
Re: Laravel 9
#24Earlier quoted context omitted.
I'm curious what you don't like about it. I work with a team of people who love it.
Facades is the one that comes up every time I ask this question.
Which is a little silly, as you can avoid them entirely if you don't like them, and use the dependency injection or helpers instead.
Re: Laravel 9
#25We have been using Laravel for over 8 years. Nothing but praise. It's a framework we could rely on. No painful upgrades and clear documentation. For us it's a pleasure to work with. I also recommend Laracasts from Jeffrey Way.
Seconded this in its entirety. Been to Laracon multiple times, use it for all my side projects (as well as startup). Has performed remarkably well and more consistently than any other experiences I've used
Re: Laravel 9
#26Could somebody say, if you are planning to embark on a new Laravel project and you have no experience, how to begin? I bought a subscription to Laracasts, and there is a "What's New in Laravel 9" series. But "Laravel from Scratch" is still on 8.
The Laravel from Scratch will still largely be applicable, the changes in 9 won't be breaking enough for you to be missing out a lot. The upgrades tend to be painless with a few small tweaks you might have to make (and those are usually described on the upgrade page).
If I were you, I'd start with Laravel 8.0 as you go through the Laracasts, and when done, go to the upgrade page of Laravel 9.0 and checkout the changes.
Re: Laravel 9
#27We have been using Laravel for over 8 years. Nothing but praise. It's a framework we could rely on. No painful upgrades and clear documentation. For us it's a pleasure to work with. I also recommend Laracasts from Jeffrey Way.
Yeah. Maybe what we love from Laravel isn't only great docs and painless upgrade process, but also the great ecosystem.
Re: Laravel 9
#28Exactly 45 minutes ago I went on Laravel docs and saw the "you're on an old version of Laravel" message on the Laravel 8.x docs. Wow, I thought, Laravel quietly dropped a major release and I didn't even see press for it.
Don't forget to watch Laracon Online, tomorrow on Youtube.
Re: Laravel 9
#29I've been programming in PHP for around 5 years. I've used vanilla PHP, full featured MVC frameworks, micro frameworks and I've been working with Laravel for around 2 weeks. Worst experience ever. The more I dig into it the more I hate it.
This doesn't match my experience at all, and given Laravel's popularity... this comment would be a lot more valuable with a why . I will say I opt out of the starter packs and Laravel Sail (their Docker-for-dummies basic setup) in favor of a more bespoke setup, but my Laravel experience has been great otherwise.
Not the OP, but one thing that stands out for me is the (lack of) quality of the documentation. It reads more like a book (that tries to explain how to do things) than a reference (an exhaustive list of all classes, methods, parameters etc.). Ok, it's nice to have the former, but the latter would be far more important!
Re: Laravel 9
#30For those here wondering why you'd use Laravel over vanilla PHP + MySQL + PDO, a few of my clients had this opinion so I've had experience. The Laravel "fluff" saves you from rewriting tons of code, helps you write test cases, and makes logic easy to follow.
One of my clients was very anti "needless vendor packages" (definitely some truth to this sentiment), but we ended up with 14 extra php files reinventing the wheel. I'd opt for the former any day.