3 ms·
React is great; many use it badly. This is a tired debate, and the author offers no solutions or practical advice. This is someone who is tired after refactorin
by nosefurhairdo 3y ago
React is great; many use it badly. This is a tired debate, and the author offers no solutions or practical advice. This is someone who is tired after refactoring a badly written react application.
I work on a badly written react application. I sometimes sift through our microservices written in go, ruby, and Java. They're badly written too. This is not an indictment of those languages or whatever framework or technology was used in those services. Business requirements change, engineers change, and refactoring doesn't give management anything to brag about so nobody gets time to clean up the mess.
Complaining about the "churn" is even more asinine. React continues to support more usecases. New frameworks and technologies are competing and challenging one another to improve. God forbid we might have to learn something new.
- wouldbecouldbe 3y agoIt was great, but feel like it gotten too complex. And this complexity invites for more options to do bad things.
- agos 3y agomany use it badly, indeed. but is React evolving in a way that makes it easier to not use it badly?
- nosefurhairdo 3y agoI don't think it's possible for a framework to do all of the following: add functionality, preserve existing functionality, and reduce the possibility of dubious implementations. Also, I do think packages like those from tanstack have made it easier to implement react well. From what I can tell, most people's bad experiences with react come from applications which incorrectly use redux or similar global state as a cache for data from the server. The new Redux Toolkit Query and similar Tanstack Query approaches to handling server state are much more manageable, and in conjunction with appropriately using URLSearchParams you can often get away with no/minimal global state. In other words, React is not the problem.