Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
@hash-table
Indeed!
I feel the whole database-backend relation in any language or framework doesn't work well yet. ORMs often simplify concepts too much and introduce complexity problems, while raw SQL lacks dryness, safety and modularity.
There's NoSQL and other persistence alternatives, but it very much feels like there is a lot of tension in how code communicates to store and retrieve persisted data, like we haven't reached a satisfying final form yet.
Some things in Eloquent just seem logical to add though... if theres a withCount method, why not a withSum or withMax for eager loading of aggregates? If saving a relation fires a saved event, why is it impossible to register events on pivots? Why is there a whereHas and a with method, but did I have to add the often requested withWhereHas through a trait?
I get that Framework & ORM maintainers are conservative when it comes to accepting new features in the core framework.
But it can still be very frustrating to work with if you need to render a graph based on a combination of a machine learning model and a complex set realtime financial data rather than "get the first post of the author with eagerly loaded tags". -
@SHA-16384 It annoys me when someone put a lot of effort into a PR which fits both the mission of the framework and is perfectly covered by tests & documentation, and maintainers deny it with very lazily written feedback.
Of course you're under no obligation to accept every PR on an open source project, but I feel like it's rude to just write one sentence and press close... It's not like it's a vague feature request without any code attached.
This might not resonate with many ranters here... but FUCK Taylor Otwell & Graham Campbell.
Like, not on a personal level. Maybe they're great to drink a beer with. But as framework devs... fuck everything about them.
Laravel seems so nice, it takes away many annoyances of developing in PHP. Collections are the array object you've always needed. The route bindings, middlewares, request validation objects, it's all sweet.
But eventually your company serves a few million customers, you run into specific performance problems or missing features on a deeper level. You open the issue tracker... and see a few hundred issues about the problems you are encountering, they already exist.
Some just have a short paragraph with a request for a feature, some complete PRs with tests in the style of the framework. All of them closed.
Reasons?
"We don't think anyone will ever need this"
"This seems complicated, you can just do <super non-DRY hacky code>"
FUCK YOU WITH YOUR TODO APP SNIPPETS AND USER-POST-ARTICLE EXAMPLES. I'M NOT BUILDING THE NEXT WORDPRESS. I'M DEALING WITH THE REALITY OF GRAPH DATABASE CLUSTERS, COMPLEX AUDITING LOGS AND A GAZILLION QUERIES PER SECOND.
Sigh... the problem with all these "simple" and "elegant" languages & frameworks is that they don't fucking scale.
Not because the language, server or framework intrinsically can't do it, but because the maintainers are stuck thinking in terms of their retarded non-realistic example apps.
I think I'll go back to my cave and write some Haskell or Rust to calm down.
undefined
fuck laravel