realworld VS js-framework-benchmark

In light of all this, it became exceedingly clear that someone else needed to step in and help. Why not me? Well, it can be me. And, after 3 months of development, I am happy to announce (again) dwayne/elm-conduit (demo), an open-source Elm SPA for RealWorld's Medium.com clone.

https://github.com/gothinkster/realworld

It's just for web app (a Todo app). Your GIS AND CLI ideas are interesting, I haven't seen anything similar to realworld for those.

View on GitHub

So what would be a better benchmark? Perhaps a "standard" "real world" app, like https://github.com/gothinkster/realworld

Or something simpler?

RealWorld example app is a full-stack application called "Conduit" that consists of a backend that serves JSON API and a frontend UI. There are numerous implementations for different languages and frameworks, but in this tutorial you will be using the Spring backend and the React frontend.

Github has millions of projects, some large fraction with more than 100 stars, so it doesn't seem like you are searching very hard. But more importantly, why "100 stars"? Stars are meaningless and arbitrary. Many developers use stars like bookmarks. I just did a quick search and noticed a project like realworld (just a demo for learning, 65 contributors) has have more stars than Bitcoin (900+ developers, perhaps you have heard of it?)

I feel you, context API sometimes overcomplicates everything. Let me introduce to you RealWorld. It is a great project that uses composition to make its structure scalable. It is actually a codebase that implements various fragments of a larger scale project such as Medium or Twitter. Check it out here: https://github.com/gothinkster/realworld. I hope this helps!

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