app-skeleton VS js-framework-benchmark

Yeah, it's pretty cool. I've been using it with Preact for a while, in my own no-compile app-skeleton. Feel free to pinch anything from the tools folder in there as well; it's a combination of "things I actually use in my projects" and "experiments I thought'd be cool". I'm particularly proud of StateMachine - it's essentially all the power of Redux and Thunk, but instead of a mess of actions and reducers, you pass in async generators as actions, and yield states as async stuff progresses.

JavaScript benchmarks are instruments for measuring the speed and effectiveness with which a JavaScript engine—such as the ones found in web browsers—can complete particular tasks. Benchmarks are used by developers and browser vendors to evaluate various engines, find places in the code where improvements are needed, and make sure JavaScript standards are being followed.

Strange then that frameworks advertise how fast they are at rendering, mutating, and creating objects in the DOM, and one of the main JS benchmarks everyone likes to measure their performance by is literally a benchmark about DOM manipulation: https://github.com/krausest/js-framework-benchmark

Oh wait. It's not strange. Because state manipulation is a largely solved problem, and even the least performant state manipulation is blazingly fast. However, presenting components in the browser's DOM is tens of magnitudes of orders less performant than anything you can throw at state manipulation.

And every single framework is busy solving one single problem: how do we touch the DOM as little as possible?

It literally says at the bottom "Data from https://krausest.github.io/js-framework-benchmark/"

The standard benchmark for js frameworks would be best: https://github.com/krausest/js-framework-benchmark