> This is just an example, obviously you can write this better in React.
The issue is people write SO much conditional logic into their react templates. Not that disabled is boolean and can be written better.
The issue is people write SO much conditional logic into their react templates. Not that disabled is boolean and can be written better.
This seems to be a 'best practice' issue as well that can be avoided through PR review. My team has been putting logic more and more into local hook files to keep components clean.
People break tables up into ~50+ files. It's crazy, and everyone does this, and its an absolute nightmare to maintain. Its 100% engrained into react culture that this is the right path forward.
React will never get better if people accept over abstraction as the right path forward.
I do not understand why everything needs to be a single page application. Sure, my current employer is behind the times in the technology we use, but honestly, we survive just fine with server side rendering and plain, ol'boring, vanilla Javascript and a little JQuery here and there.
Of course, some things we have written are difficult to maintain at times, but I doubt any other library would have really made it simpler (more of an issue with the requirements than the technology). Abstraction is simple, for us at least.