The Past, Present, and Future of Virtual DOM

1

Svelte

Turns out, Tom Dale's bet was right. The JavaScript ecosystem has seen the rise in no Virtual DOM "compiled" libraries like Solid and Svelte. These libraries skip unnecessary computation by using a compiler to perform work beforehand, reducing the amount of data that needs to be processed. The output of these compilers are progressively enhanced, meaning code is only generated if it's needed.

#Javascript UI Libraries #JavaScript Framework #JS Library 353 social mentions

2

React

The Virtual DOM was initially pioneered by the React authors to make declarative UI faster to render. To understand why declarative UI was originally so slow, we first need to understand how declarative UI was done in the past.

#Javascript UI Libraries #JS Library #JavaScript Framework 775 social mentions

3

Million.js

In this exercise, we will mimic the ✦ Million.js Virtual DOM API. Our API will consist of three main functions: m, createElement, and patch.

#Web App #Developer Tools #GitHub 13 social mentions

4

ember.js

Tom Dale, the creator of Ember, was one of the first JavaScript UI library zealots to advocate for the use of compilers for JavaScript UI libraries.

#Javascript UI Libraries #JavaScript Framework #JS Library 27 social mentions