Next, I'd like to discuss WildflowerJS's performance vs other reactive frameworks.
TL;DR: it does very well on the official Krausest benchmark.
How does a no-build (no compile step), no virtual DOM framework stack up? Well, currently, it bests all _full-featured_ frameworks (
data-list is level with Vue Vapor 3.6-rc.5) in Krausest benchmarks (see attached). Just to be clear: 1) this is the official Krausest benchmark, you can see the results now in the official chart. 2) we compare against full-featured frameworks because we have the full feature set expected of reactive frameworks.
So there are a couple of reasons why this is possible:
1) direct binding between data-bind and the DOM node it controls, with no tree to diff.
2) The work a compiler does in other frameworks happens in a _very_ quick pass at runtime, recording where bindings live in lists and building small specialized setters. (Remember, while the compilers in other frameworks also do this, they also have to translate the non-standard code to HTML and JS. In WF you write standard HTML and JS; a compile step is not needed.)
3) Every framework change that could possibly touch and affect the hot path is evaluated and benchmarked to make sure it doesn't.
4) Benchmarking was part of the development process from the very start.
Even though this is no-build, this all happens without eval, so our Krausest runs are also CSP-safe. It was questionable whether this would affect the benchmark results, and if we'd have to run without CSP-safety, but it had a negligible effect on the scores.
We also have two entries, because of our two reactive modes. Data-pool is for high-throughout reactivity, but it also is perfectly capable of rendering simple lists with very little addition to the developer's workload, so we included it. But optimizations to our data-list (standard) reactive path have brought it very close to our pool implementation for simple lists.
You can see the full benchmarks here:
https://krausest.github.io/js-framework-benchmark/2026/chrome154.html
The attached chart and an interactive to compare the various individual benchmarks are on the homepage: https://www.wildflowerjs.com/
Any questions, please ask!krausest.github.ioJavaScript Framework Benchmark — Interactive ResultsExplore JavaScript framework benchmark results. Compare execution time, memory use and bundle size across keyed and non-keyed implementations.
commit ff98e7f