React is a web framework. Like everything else it has some good points (popularity) and bad points (performance, support cost).
When you get more experience, one thing you’ll learn is that when “literal hell” isn’t entirely untrue it’s a social problem. If your organization isn’t good at maintaining a large application, a tool won’t save you. It’s very common for people to look at problems and blame the current tools because that’s where the symptoms are and, critically, it doesn’t require saying anyone needs to be doing a better job managing the project.
JFC, "when you get more experience". If you people are going to be throwing around this bs you better have your linkedin on your profile and you better have 20 years of experience.
edit: Which you do, touche. That being said, I'm experienced, I'm just hyperbolic and emotional about things. Not everyone that's experienced has that "cool, I've done this a million times before" demeanor ok.
Let’s just say my first for pay project was working with a custom Gopher server and I played around with JavaScript when it first came out in beta with Netscape Navigator…
Okay, I’ve been writing JavaScript since before it had that name so you’re only low by 7 years or so.
Again, I’m not saying that React is horrible – only that people are prone to misattribution leading to overstating the benefits of their current favorite tool relative to other factors. That works both ways, too: it’s not uncommon for people to credit a newer tool for productivity improvements due to their skills increasing over the same time period.
When you get more experience, one thing you’ll learn is that when “literal hell” isn’t entirely untrue it’s a social problem. If your organization isn’t good at maintaining a large application, a tool won’t save you. It’s very common for people to look at problems and blame the current tools because that’s where the symptoms are and, critically, it doesn’t require saying anyone needs to be doing a better job managing the project.