A general programming discussion community.
Rules:
- Be civil.
- Please start discussions that spark conversation
Other communities
Systems
Functional Programming
Also related
- 0 users online
- 3 users / day
- 7 users / week
- 40 users / month
- 135 users / 6 months
- 1 subscriber
- 345 Posts
- 547 Comments
- Modlog
If you want to use PHP, and you want to be productive, there’s no other choice in my opinion. I will say, the brain behind it is quite opinionated and most of those opinions are correct. If you don’t agree with those opinions, you will probably find yourself hating it and fighting the Laravel Magic. Give in to the magic and get shit done.
I use PHP daily. The only thing that seems overly magical on a cursory glance is Livewire, but I’ll probably end up using Solid for the frontend anyway.
Yeah, we tried using Livewire at work, wouldn’t recommend it for any usecase. Very buggy and unfinished, many times you’ll still need to fallback to JS, passing certain data types to Livewire components is just not supported.
I, and then every junior I’ve onboarded as well, struggled to grasp just how important the naming conventions are for everything to just work. Models and tables must be named a certain way or you’ll be scratching your head. Model policies must be named a certain way. On and on. You can override all those, of course, but it’s just another gotcha.