Stefan Krause

@paulfalgout I understand your point and I hesitated to mark those implementations for a long time. But what we want to measure is the performance of a framework, not the...

@paulfalgout Do you have a suggestion how to handle that situation better? In the spirit of the benchmark it should be our goal to flag e.g. a react implementation that...

@paulfalgout I updated the [results](https://krausest.github.io/js-framework-benchmark/current.html) table similar to @ryansolid 's suggestion. I couldn't pick up your idea with the opposite naming yet, but I'm looking into it.

@paulfalgout @ryansolid This could be the positive wording for the selection. Of course I'm open for better wording. @ryansolid One major drawback: You'd have to get used to click "All"...

Dare to give some details?

Yes, this was reported in #532 (it doesn't compile. But if it would I swear the html would be correct :-) I'm afraid not all implementations build on windows natively...

Nice! It‘s indeed the geometric mean. I felt it makes more sense for a average of factors.

Maybe vanillajs-#2 would be better :rofl: (was created due to #403) I always wanted to get back to a single vanillajs implementation, but I haven't managed to decide which one...

The only thing better than one vanillajs implementations would be several vanillajs implementations :smile: but with clear and distinct implementation strategies (and appropriate naming). So I'd say we should take...

That difference looks worrying! As a first quick check I ran a single create rows benchmark for a few frameworks. I got the following results: Could indeed be that the...