1
Nmeri17
206d

A few days back, I was battling to setup a spring app the old fashioned way. By that, I mean the way I'm used to securing routes in laravel and indicating model relationships. For the most part, I'd gotten used to the authentication config more than my first experience with it

But the jpa/hibernate relationship mess? Honestly, it's insane. If I can only access the relationship if I let them be defined eagerly (which stupidly breaks due to circular dependencies during deserialization btw), what's the point even bothering to define them there? Might as well pretend the relationship doesn't exist and strictly use IDs on belongsTo. That's it. At the time, it felt like Very sick, amateurish stuff but I'm calmer now so it's just disappointing. How come the framework is so popular??

They haven't figured out migrations, lazy and eager load, hydrating models while evading the circular dependency trap, etc. These seem so rudimentary in eloquent, I don't even have to think about it

Comments
Add Comment