The primary reason for abstractions to DOM methods like jQuery and MooTools was the inconsistencies of browser behavior especially during the browser wars. IE, Netscape, Mozilla, Opera, Safari, all of them had their quirks and issues. Later then target of these toolkits shifted to a better developer experience.
Then Google released Chrome with V8, delivering a hitherto unknown performance to the web, which led to a paradigm shift, to web apps. Not web sites simulating actual apps, but application logic in the front end. With this shift, a lot of patterns previously reserved for the back end were moved to the front, bringing the first attempts to have MVC patterns in the browser.
These patterns were refined and adapted until we reach the current situation where concepts like virtual DOM, data binding, state management, components, JSX and so on can be used freely, either as part of a framework or mix and match of specialized tools.
Million.js is such a specialized tool for a virtual DOM. There are others, like inferno and frameworks that forgo the virtual DOM approach completely.
100% agree with first couple points. I believe you have a fundemental misunderstanding of Inferno, they're currently one of the fastest frameworks with vdom libraries - they dont forgo the Virtual DOM at all 😂.
No, you misunderstood me: other vDOM libraries like inferno and those that forgo the vDOM like Solid or Svelte. Though I concede it was easy to overlook this detail.
The primary reason for abstractions to DOM methods like jQuery and MooTools was the inconsistencies of browser behavior especially during the browser wars. IE, Netscape, Mozilla, Opera, Safari, all of them had their quirks and issues. Later then target of these toolkits shifted to a better developer experience.
Then Google released Chrome with V8, delivering a hitherto unknown performance to the web, which led to a paradigm shift, to web apps. Not web sites simulating actual apps, but application logic in the front end. With this shift, a lot of patterns previously reserved for the back end were moved to the front, bringing the first attempts to have MVC patterns in the browser.
These patterns were refined and adapted until we reach the current situation where concepts like virtual DOM, data binding, state management, components, JSX and so on can be used freely, either as part of a framework or mix and match of specialized tools.
Million.js is such a specialized tool for a virtual DOM. There are others, like inferno and frameworks that forgo the virtual DOM approach completely.
100% agree with first couple points. I believe you have a fundemental misunderstanding of Inferno, they're currently one of the fastest frameworks with vdom libraries - they dont forgo the Virtual DOM at all 😂.
You probably mean libraries like Solid or Svelte
No, you misunderstood me: other vDOM libraries like inferno and those that forgo the vDOM like Solid or Svelte. Though I concede it was easy to overlook this detail.
I see now, thanks for the clarification