2 ms·
I'd have to agree; React is pretty cool in some use cases but it's not always the best tool for the job. I mean take a look at the Atom editor; they initially u
by BinaryIdiot 11y ago
I'd have to agree; React is pretty cool in some use cases but it's not always the best tool for the job. I mean take a look at the Atom editor; they initially used it which helped speed up their development but after a certain point they benchmarked it and found simply manipulating the DOM itself was far faster. Now that doesn't mean to never use React; all that means is simply use the right tool for the right job.
If you need something done and done fast with decent code separation, feel free to pick up React. If you need to optimize for performance (because many of us need to at some point) or you have a good understanding / way to architect your code to keep up a good separation of DOM and business logic then use almost anything else.
Hell, you don't even need to use a framework for the web. My last project I didn't use any and it was perfectly fine. Frameworks are great to get you going faster and doing the hard parts for you but you don't always need that.
In my opinion anyway.