React feels insane

9:17 Drawing Angular as less scalable to complexity than React is so insane I choked on my drink.

Theo, it's me, your only viewer. Over the years, I've created the illusion that many people were watching you, but it was all me. Now, I will send this message from all of my accounts.

This author has 50 inherits on his Button and calls it "clean code". Honestly I think the problem nowadays is that a lot of people are exposed too early to OOP design patterns and lack the knowledge to apply them correctly. The same people who take "DRY" as literal as possible, and are somehow afraid of putting code in the same file. And then try to reflect that onto something like React whose _principles_ are simple (yes it has "complexity", but those usually serve to common hard problems you'll encounter when developing a larger application). It's sad really. I've learned a lot since I started using more simple languages that doesn't even support inheritance, just data and procedures. Yes you pass every dependency down; it's explicit, clear, easily traversable and easy to debug. And I use the same ideas for React code. It's ok to prop-drill and not having to rely on spooky action at a distance.

This angular discussion feels entirely based on people’s perceptions of very old versions of Angular…18, 19, 20 are just so good.

I don’t know I’m a huge react fanatic, but I really understand how people can end up with a perspective like this. Virtually every large react code base I get into seems to get worse the larger it gets

"HOCs, no one does this anymore" - forgets that 90% of the apps from that time are still alive and we have to maintain them and still add new features constantly

as someone migrating from angular to react, being told that angular is less suitable for high complexity apps than react makes me laugh. there is areas of complexity that would be easier to handle with angular, specially what has some built-in tool to help. its just different areas of complexity that angular and react handle better, but both handle some pretty complex stuff, just different kinds of complexity.

26:10 THIS is the exact problem with React. That you are allowed to do this, and no one is actually going to tell you not to. You can even watch tutorials that would use useEffect for that. This is precisely why I hate it so much. There are so many different ways to solve issues that _inevitably_ either one of your colleagues, or your entire company will just keep going in the direction that you find stupid. And you cannot stop it, because it _is_ an accepted option in the React world.

Sounds like React is going through similar criticism to PHP. Rule #1 - Don't get emotionally attached to software. Rule #2 - Just because you're good at something, don't insult the intelligence of those that don't like your approach - learn from them. Rule #3 - Shitting on other people's projects says more about you than them or their projects. Primeagen and Theo are getting just a little too emotional about this stuff.

I'm pretty sure this whole "Don't use useEffect for events" is a very recent thing. For the longest time in the React docs it was completely silent about this, and so lots and lots of people used useEffect to trigger things like fetch requests when state changed... This was taught this way by lots of tutorials.