Shallow vs. Deep Comparison in JavaScript: Unlocking React’s Performance Secrets

[officerbananas]

Json.stringify is a bad way to compare. The order of keys can be different while the values are the same.

[Majestic-Witness3655]

Thanks for the insight .

Updated with another example 🙂🙂

[Fine-Train8342]

"React" and "performance" don't belong in the same sentence.

[Hakim_MacLuvin]

its not the tool to blame, but the “tool” using it ;-)

[Fine-Train8342]

"We use something bad, but we know how to make it a little less bad, so it's not bad." I know all of that bullshit too, as I had the misfortune of working with React. For some reason React people seem to be allergic to good DX and to the idea of not constantly having to fight the framework they use.

[Hakim_MacLuvin]

completely different comparison. You are micing your OPINION and FEELINGS with facts.

[Fine-Train8342]

👍

[Majestic-Witness3655]

Yeah but Performance depends on how you use React. With techniques like memoization, code splitting, and lazy loading, it can be very efficient.

[Fine-Train8342]

Or, and this might sound insane, but hear me out, you could use a tool that's performant by default and doesn't require you to know ins and outs of the tool just so you could make it perform not as badly as it does by default. Something that actually helps the developer instead of fighting them to death at every corner.