Re: [whatwg/dom] Proposal for built-in method to synchronize elements with virtual DOM representation (Issue #1213)

As a virtual DOM library dev who's been in that field for almost a decade, I would like to advise some serious caution here, especially for frameworks and libraries other than React. (React's internal design is very different from most others'.)

Feeding literal trees is only half the battle. There's other child types common across virtually every virtual DOM implementation. To name a few:

- Components
- Keyed map fragments
- Fragments linked to single keys
- Fragments not linked to keys at all

Most of the code of a virtual DOM library isn't the immediate methods, but in trying to find ways to not update the DOM. And in frameworks with the highest performance like Mithril.js, Vue, and Inferno, the very act of invoking DOM methods is itself very observable in profiles.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/dom/issues/1213#issuecomment-2373856741
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/dom/issues/1213/2373856741@github.com>