js-framework-benchmark
solid
Our great sponsors
js-framework-benchmark | solid | |
---|---|---|
64 | 20 | |
6,468 | 5,767 | |
- | - | |
9.8 | 9.3 | |
7 days ago | almost 3 years ago | |
JavaScript | TypeScript | |
Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
js-framework-benchmark
-
Popularity is not Efficiency: Solid.js vs React.js
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.
-
Use any web browser as GUI, with Zig in the back end and HTML5 in the front end
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?
- JavaScript-Framework-Benchmark
- GitHub - krausest/js-framework-benchmark: A comparison of the performance of a few popular javascript frameworks
- JavaScript Framework Benchmark
- Vue 3 now outperforms Svelte and React
-
Vue 3 is currently performing better than Svelte and React
It literally says at the bottom "Data from https://krausest.github.io/js-framework-benchmark/"
- Cample.js benchmark reactivity without VDOM
- Rust é uma linguagem que embora tenha uma curva de conhecimento considerável, entrega vários benefícios como segurança e produtividade, reduzindo consideravelmente a verbosidade
-
Imperative - 1.5kb React alternative using Generators
The standard benchmark for js frameworks would be best: https://github.com/krausest/js-framework-benchmark
solid
-
Why Virtual DOM is considered faster that directly updating the real DOM.
The strength of V-DOM definitely doesn't lay in performance. It made it easier for developers to write more maintainable interactive UI. Other than that I'd rather think of it as a compromise. Fortunately, frontend web dev continuously progresses and there are initiatives like https://github.com/ryansolid/solid which focus on compilation-time diffing.
-
Learning to Appreciate React Server Components
You see I work 12 hours a day. 8 hours of that is my professional job where I am a developer on the Marko core team at eBay. Then after some much-needed time with my family, my second job starts where I am core maintainer of the under-the-radar hot new reactive framework Solid.
-
Hyperapp – Is It the Lightweight 'React Killer'?
They’ve been well received, and the core ideas behind them have inspired the likes of Vue’s Composition API and a big part of Solid’s API.
- Solid Update: March 2021
-
Introducing maple, a VDOM-less fine grained reactive web framework in Rust + WASM
After discovering solid js, I wondered how feasible it would be to write such a framework in Rust. After two days of hacking around, here is the result!
-
Introducing maple, a VDOM-less fine grained reactive web framework running in WASM
After discovering solid js, I wondered how feasible it would be to write such a framework in Rust. After two days of hacking around, here is the result!
-
[AskJS] Any interesting use cases for Proxy?
Solidjs UI library uses Proxies in order to make state reactive https://github.com/ryansolid/solid
-
[AskJS] What you love about Javascript that we don't find in another programming language and why many OO programmer from others language Java, C#, C++ etc hate/don't like it ?
[0] https://github.com/ryansolid/solid#the-gist
-
Server Rendering in JavaScript: Optimizing Performance
The key thing to understand though is this is not a React-only approach. I make heavy use of this pattern in my Solid projects as it makes a really nice isomorphic solution and works really well with the next topic...
-
Building a Reactive Library from Scratch
The main ones that I'm referring to have proxy implementations along with their basic signal atoms. MobX's `observable`, Vue's `reactive`, Solid's `state` all are reactive proxies that properly handle subscriptions.
What are some alternatives?
mikado - Mikado is the webs fastest template library for building user interfaces.
Svelte - Cybernetically enhanced web apps
sycamore - A library for creating reactive web apps in Rust and WebAssembly
marko - A declarative, HTML-based language that makes building web apps fun
yew - Rust / Wasm framework for creating reliable and efficient web applications
morphdom - Fast and lightweight DOM diffing/patching (no virtual DOM needed)
imba - 🐤 The friendly full-stack language
rust-dominator - Zero-cost ultra-high-performance declarative DOM library using FRP signals for Rust!
solid - A declarative, efficient, and flexible JavaScript library for building user interfaces.
hyperapp - 1kB-ish JavaScript framework for building hypertext applications
knockout - Knockout makes it easier to create rich, responsive UIs with JavaScript