blockdom
ivi
blockdom | ivi | |
---|---|---|
5 | 3 | |
519 | 684 | |
- | - | |
4.6 | 8.6 | |
8 months ago | 6 months ago | |
TypeScript | TypeScript | |
MIT License | 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.
blockdom
-
Unleashing Million.js v2.0.0
blockdom (Géry Debongnie) Thank you to Géry pioneering the concept of "blocks" in the virtual DOM. Many parts of the Million.js codebase either directly or indirectly derive from his work.
-
React creates better user experience?
this is 100% false, look at the js framework benchmark and u'll see that vanilla-js with DOM is faster than any other framework and almost twice as fast as react. not that VDOM is slow its just that react's implementation is slow. blockdom for example uses VDOM and its very close to vanilla's performance
-
Exploring Blockdom: Fastest Virtual DOM (ever!)
If you've been around in the JavaScript UI library development space, you've likely heard about blockdom, which claims to be probably the fastest Virtual DOM that currently exists.
- Tutorial "Make your own framework": 250 loc, with components, reactivity, effects, scheduling, ...
- can a virtualdom beat solid js? introducing blockdom, a fast virtualdom library
ivi
-
Unleashing Million.js v2.0.0
ivi, Preact, and more
-
Components are Pure Overhead
And the answer was: it depends. The Virtual DOM library I tested, ivi, had no issues handling more components. But Lit and Svelte were dramatically worse. They scaled back to almost React levels of performance as I broke them down to more components. All their non-VDOM performance benefits basically disappeared.
-
[AskJS] Why are large, sprawling functions more common than small, compact ones?
Some things are just inherently complex. Look at virtual dom reconciliation algorithm, for example. Others simply don't benefit from overly aggressive pursuit of "improvements". Look at database levels of normalization for another example of how one can apply theoretical "best practices" to the wazoo and completely lose sight of pragmatism.
What are some alternatives?
snabbdom - A virtual DOM library with focus on simplicity, modularity, powerful features and performance.
hundred - Build your own mini Million.js
virtual-dom - A Virtual DOM and diffing algorithm
superfine - Absolutely minimal view layer for building web interfaces
million - Optimize React performance and make your React 70% faster in minutes, not months.
import-cost - displays the import size of the package you are importing inside the code editor
webcomponents - Web Components specifications
Torque3D - MIT Licensed Open Source version of Torque 3D from GarageGames
React - The library for web and native user interfaces.
Svelte - Cybernetically enhanced web apps
ctrl-keys - A tiny, super fast, typescript library to handle keybindings efficiently.
voby - A high-performance framework with fine-grained observable-based reactivity for building rich applications.