1. The benchmarks aren't always going to be fair - e.g., in this article they talk about rendering 3,000 rows, but that's an unrealistic benchmark (you'd want to use list virtualization in any framework at that point) that is obviously more favorable to some frameworks over others.
2. Most frameworks are fast enough for most tasks. The performance of a framework is rarely the main issue, but benchmark scores are quantitative and sound objective, so people cling to them.
2. Not really, but also you've stretched "enough" into a very low bar. Sure, hardware has progressed enough to mask a lot, until you get slower laptops, untill those also get fast enough, until you get phones, until you wait another decade for phones to catch up, until you get some wearables etc.
> so people cling to them
Except they don't? It's extremely rare to see proper widespread UI benchmarks. This post only covers a few frameworks. I challenge you to link to more comprehensive ones that are widely "clinged to", and let them also have a wider range of UIs/UI operations to measure