Looking at laravels source code and organization

It's horrible, right? It breaks so many conventions, doesn't comply with solid principles, uses magic methods and contract-breaking traits al over the place. Higher order messages are awfully implemented, Eloquent tightly couples DB queries to classes which are both entities and domain models, and PHP is horrifically unsuitable to cram in some half assed FP paradigm... I have too much hate for this mess of a framework 😤

Working on a >20 million line big project... you start to see that Laravel is a pretty uncoordinated ugly mess, with a sweet magical layer of icing.

The pretty stuff works great for small / medium sites... but not for large platforms.

@bittersweet yeah then again large platforms shouldn't be using MySQL and PHP 😁

@n3xus Facebook managed... although they did build several abstraction layers on top and built their own interpreter.

Please, shoot me some alternatives though. What would you use for a complex statistical/aggregating backend with more than a million users.

I'm really curious what other people consider their "ideal" backend stack. ☺️