So one dev in my team decided to use Laravel for a project, which no one else has experience with. I'm not sure if it's standard or not, but there seem to be a lot of static stuff being used. Is that the preferred way, or just something new people can do who don't know any better?
this post was submitted on 21 Jun 2023
1 points (100.0% liked)
Laravel
174 readers
4 users here now
Laravel is a web application framework with expressive, elegant syntax. We believe development must be an enjoyable and creative experience to be truly fulfilling. Laravel attempts to take the pain out of development by easing common tasks used in most web projects.
This community aims to be a place for all things Laravel.
#Recommended links
founded 1 year ago
MODERATORS
Laravel definitely uses a lot of static method calls. We use User::find($userID) to pick out a user and the Eloquent ORM uses static calls in the form User::where('name', 'Jim')->where('age', '>', 20)->get() etc.
Stuff like Facades really spook me since there's got to be a better way.
What is it about them that's a concern? Some specific use my your coworker that seems nonstandard?
I just don't like using static classes, that's all.