Julian SomesanFeb 27
github.com/ghostwriter
#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.
Feb 26 at 9:57pmWeb
Show threadDavid PeachFeb 26
@ghostwriter what are the things that have stuck out the most that you've found?
Show threadgithub.com/ghostwriterFeb 27

@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)

Show threadEvert PotFeb 26
@ghostwriter it's the apple marketing playbook
Show threadEvert PotFeb 26
@ghostwriter also being bothered about how Laravel markets itself is an ancient PHP community. Nice to know some things never change 😅
Show threadjoachimFeb 26
@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!
Show threadjoachimFeb 27
@ghostwriter It's annoying, but also, it's crappy DX and it's a mental load having to learn all these random names.
Show threadgithub.com/ghostwriterFeb 27

@joachim Yeah, installing ~20 packages just to get a handful of commands and a couple endpoints when that functionality could easily live in the framework itself.

Instead of the name telling you what it does, you have to memorize a bunch of branding terms first.

It often feels like things are split into separate packages because shipping a “new package” looks more innovative than just adding a solid feature to the core…😅

Show thread.:\dGh/:.Feb 26
@ghostwriter Not giving a crap as long it pays de bills.