realworld VS js-framework-benchmark

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?)

Here’s a roster of implementations for the same basic app https://github.com/gothinkster/realworld in a variety of frameworks. While you’re at it, it might be worthwhile showcasing Kobweb. There are a couple of entries for Kotlin.

Finally, once you finish most of these tutorials, I recommend you taking a look at gothinkster/realworld, specifically taking a look at React + Redux for the frontend and Spring Boot + Spring Data JPA.

2. Realworld

- https://www.realworld.how/

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

I ran it locally and measured 70MB. I filed a bug for clarification: https://github.com/krausest/js-framework-benchmark/issues/1231

As far as performance between interpreted and AOT, Krausest’s JS benchmark project installs the wasm-tools workload for both, which will do runtime relinking whenever the project is compiled with the Release configuration. From what it looks like on the network traffic side of it, the IIS config they’ve got does not seem to include rewrite rules to serve the Brotli or gzip files and is pulling the uncompressed files at startup instead. I rarely use IIS and instead use Kestrel (Usually in a container that gets proxied from a nginx server) or nginx, so I could be wrong about that.

Anyway you can counter with: https://krausest.github.io/js-framework-benchmark/ Vue is way ahead angular here.

Right here man, https://github.com/krausest/js-framework-benchmark Results are not good for Blazor. Rust WASM frameworks are about on par with the JS ones now a days.

All libraries use procedural macros to create a JSX like syntax. In Yew and Leptos it’s more HTML-like while for dioxus and Sycamore it’s a bit more Rust-like. I think Dioxus, Sycamore and Leptos are all about as fast as Vue (or faster) according to that Frontend framework benchmark (Yew is comparable to React). Dioxus v0.3 results aren’t there yet but are a huge improvement: https://dioxuslabs.com/blog/release-030/