5 ms·

I work a lot with Laravel, it is a hell of a framework, documentation is amazing, it's clean, very well done, super extensible, there are a lot of extensions (j

by moray 8y ago

I work a lot with Laravel, it is a hell of a framework, documentation is amazing, it's clean, very well done, super extensible, there are a lot of extensions (just have a look at the Spatie library) and allows me to build up a website/webapp backend with a good API, basic authentication and other basic features in minutes. Also, and this is a really strong point, can manage assets super easily, React and Vue stacks are supported out of the box with laravel-mix. And if you need something lighter (for building just an API for instance) Lumen is the light version of it. I have a lot of experience with PHP and Python frameworks, Laravel comes as absolute top for me. https://laravel.com/ https://laravel.com/ https://spatie.be/open-source https://spatie.be/open-source https://lumen.laravel.com/ https://lumen.laravel.com/

fimdomeio 8y ago
Yes. That's probably the main reason why I keep developing in php. The fact that Laravel and Lumen are so well thought out.
chiefalchemist 8y ago
As someone who recently took on the Laravel learning curve, be aware that Laravel moves atypically fast. That is, something in say version X.Y might be different in X.Y+1 or Y+2. That ends up manifesting itself as a lot of noise when you're asking The Google for help. It can be frustrating. When you're on a deadline it can be unnerving and then some.
- tomschlick 8y ago
  That's true for additional features, but rarely does documented behavior change in a point release. That usually only happens when there is a security bug.
  - CleanShirt 8y ago
    That’s not true. It happens quite often. Variables, classnames, php targets are changed on a whim.
  - chiefalchemist 8y ago
    More than twice The Google found me solutions that were out of date by Y+1 or Y+2. I finally got into the habit of making sure what I found was current. But that doesn't prevent so much noise in the Laraval + The Google signal.
- TheRealDunkirk 8y ago
  Ha ha. Joke's on me. I just inherited at 3.x site. Getting it upgraded to 5.5 looks like it will be a half-total rewrite.
  - CharlesW 8y ago
    If you can get it to 4.2, you may find this helpful: https://laravelshift.com/ https://laravelshift.com/
tonysickpony 8y ago
Thanks man. I have heard a lot of good words of laravel. Will definitely have some experiment with it.

by moray 8y ago

fimdomeio 8y ago

Yes. That's probably the main reason why I keep developing in php. The fact that Laravel and Lumen are so well thought out.

chiefalchemist 8y ago

As someone who recently took on the Laravel learning curve, be aware that Laravel moves atypically fast. That is, something in say version X.Y might be different in X.Y+1 or Y+2. That ends up manifesting itself as a lot of noise when you're asking The Google for help. It can be frustrating. When you're on a deadline it can be unnerving and then some.

tomschlick 8y ago
That's true for additional features, but rarely does documented behavior change in a point release. That usually only happens when there is a security bug.
- CleanShirt 8y ago
  That’s not true. It happens quite often. Variables, classnames, php targets are changed on a whim.
- chiefalchemist 8y ago
  More than twice The Google found me solutions that were out of date by Y+1 or Y+2. I finally got into the habit of making sure what I found was current. But that doesn't prevent so much noise in the Laraval + The Google signal.
TheRealDunkirk 8y ago
Ha ha. Joke's on me. I just inherited at 3.x site. Getting it upgraded to 5.5 looks like it will be a half-total rewrite.
- CharlesW 8y ago
  If you can get it to 4.2, you may find this helpful: https://laravelshift.com/ https://laravelshift.com/

tonysickpony 8y ago

Thanks man. I have heard a lot of good words of laravel. Will definitely have some experiment with it.