What if we droped the non-keyed frameworks?
Author: krausestCreated Jul 27, 2026Updated Aug 3, 2026
I thought AI meant that JS frameworks were getting less focus and thus this benchmark would slowly fade out. I was wrong. Frameworks are popping out like never before:
| Chrome Version | # Keyed frameworks |
|---|---|
| Current | 179 |
| Chrome 150 | 171 |
| Chrome 148 | 163 |
| Chrome 146 | 159 |
| Chrome 144 | 154 |
| Chrome 142 | 151 |
| Chrome 130 | 157 |
| Chrome 130 | 157 |
| Chrome 120 | 135 |
Running the benchmarks will become pretty much impossible when the count continues to increase.
I'll have to come back to ideas how to reduce the framework count:
- Ignore (i.e. don't run) the non-keyed frameworks. The worst part of the non-keyed section is that it somehow forces keyed frameworks to submit a non-keyed implementation too.
- Keep research level frameworks only for a short period. Frameworks with less than 30 github stars could be removed after 3 months (both numbers are subject to change)
- Feel free to add better ideas...
Source: krausest/js-framework-benchmark