Just gotta write your CSS carefully. It's not easy, it takes time to learn, but so does the constant juggling that is the React world. At least the first one is faster and won't be out of fashion in 5 years, since it hasn't been in a decade.
I also find separation of concerns conceptually more sound and powerful.
Not at all, React is still a juggernaut and the industry standard. It is really, really good at what it does and other libraries are often riffs on its design philosophy. Even if React itself goes away for some reason, those patterns are here to stay since it has left a permanent mark on the field.
These complaints sound a bit like saying "man, compilers are so complicated, hopefully this trend is dying and we can get some sanity back."
It's an interesting comparison. An optimizing compiler is an incredibly complex beast that makes developer's life almost incalculably better. Most of our stack would be unfeasible to write and maintain in assembly. I'm not at all sold that React remotely qualifies, in fact, I've yet to see any benefits to developers or end users.
> Most of our stack would be unfeasible to write and maintain in assembly.
The same can be said about libraries like React and websites. Honestly, your position is completely untenable because it's the classic "everyone is dumb except me." Ah yes, all these million and billion dollar companies decided to use React because they're bored and not because it brings any value. You're the only genius, if only everyone realized that the Ideal Website was just handcrafted js.
There are thousands of websites written in React today, and they bring value to their users. That's not disputable. To suggest that there's no benefits is just an astounding level of arrogance.
I’m far from being the only one and it doesn’t take a genius to see that our industry is driven by far more than objective value returned to developer or end user.
Just do a quick search on HN, Twitter, Mastodon. You’ll see that’s actually not at all hard to find articles questioning its effectiveness.
The epiphany I had a few years ago is that React is very good for hiring, being hired, managing a team and has very little to do with writing and maintaining a website. At least that’s what I tell myself to find some peace. If you don’t think the JS world is mad, I don’t know if I can convince you in a HN thread.
It’s actually fine and great and decently performant for making web apps. Declarative code is much nicer than mutating the DOM, components are a great way to reuse code compositionally, hooks are nice building blocks for reusable logic within them. The JS world is indeed mad but that doesn’t mean React isn’t a highly pragmatic way of building GUI applications.
Just because style, logic, and result are logically grouped it doesn’t mean you’re losing “separation of concerns”. If in fact your definition of that is so shallow it amounts to simply having things in different files, you can do that anyway. It’s an organisational choice.
If your components are large enough to warrant this simply break them down.