Re: [whatwg/dom] Proposal: DOMChangeList (#270)

> Right now it feels like we're solving a specific use case (e.g. the Virtual DOM diff + patch model), which may prove unwieldy when people aren't building that precise functionality.

Just to make sure we're all on the same page, Glimmer does **not** use a VirtualDOM diff + patch model. It doesn't maintain its own representation of an intermediate not-real DOM, and does not diff two not-real DOMs in order to determine what operations it needs to perform.

I know of at least three models (Google's Incremental DOM, React's Virtual DOM, and Ember's Glimmer VM approach) that provide write-only abstractions that can identify a list of changes to apply, and then apply them in a batch.

That doesn't **necessarily** mean that the requirements of those systems are general purpose (and I strongly agree with your concern about unnecessarily coupling solutions together), but the solution is not tightly coupled to the diff/patch approach used by React and similar approaches.

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