#Laravel often ignores widely accepted best practices for a long time, and then when it finally adopts them, it presents the change as if it just discovered something new… even though the broader #PHP community has been pointing out the issues for years.
-
@ghostwriter what are the things that have stuck out the most that you've found?
-
@ghostwriter it's the apple marketing playbook
-
@ghostwriter The thing that bugs me with Laravel (so far) is the batshit meaningless names they have for the components. Manage your database with Sailboat! Create CLI tools with Artichoke!
-
@ghostwriter Not giving a crap as long it pays de bills.
-
@ghostwriter it's the apple marketing playbook
@ghostwriter also being bothered about how Laravel markets itself is an ancient PHP community. Nice to know some things never change
-
@ghostwriter what are the things that have stuck out the most that you've found?
@peach too many things.
type declarations, traits (everywhere), no final, attributes, facades, eloquent (magic everywhere/god class), Macroable, No strict typing ( Girgias/unify-typing-modes-rfc passes), Bad encapsulation (protected memebers because everything "extends" something) tight coupling, global function (namespace please), Dependency Injection (composition)
-
@ghostwriter The thing that bugs me with Laravel (so far) is the batshit meaningless names they have for the components. Manage your database with Sailboat! Create CLI tools with Artichoke!
@ghostwriter It's annoying, but also, it's crappy DX and it's a mental load having to learn all these random names.
-
R relay@relay.infosec.exchange shared this topic
