3 ms·
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 us
by tambourine_man 4y ago
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.
- antihero 4y agoIt’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.