2
Nmeri17
1d

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
  • 4
    Certain frameworks are popular pure, pure by incompetence. Bad things I say about Rust are not serious. But about REACT... Oh my god, if you don't have any feeling that you're doing smth completely wrong, I just give up. Unable to heal. React actually costs quite some learning that could make people feel smart but it's actually a lot of learning because it just really sucks. I started developing where the only job of a frontend was adding a date picker to the page and refusing to do design stuff because he was a "frontender" what totally had no definition back them . They created their own jobs. Believe me, it was all rainbows, ponies, unicorns with and without horn and chickens crossing the street.

    But yeah, now we're having this situation. It's so interesting, every beginner is like "what should I learn?". Well, kinda everything, your learning skills regarding tools develop. But then they all be like: OK, let's do REACT. Aaaaaaaaaaaargh. The rule to the exception.
Add Comment