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

> Can we separate these into two distinct proposals - one for async application of layout and another for DOM mutations on worker threads?

I think I mentioned earlier there is value in having these combined, since it means that the API and programming model you end up with is shared, meaning abstractions can also be reused, etc.

> I do think we need a way to spread the style, layout and paint steps inside the browser out over several frames. 

But should it be up to the browser to decide which nodes get rendered when? I think developers would want control over what is included and what is not. The tight coupling of various disciplines is what worries me most about the "async append" proposal. It seems counter to the extensible web lessons.

> I'm not convinced that doing that requires building an integer based abstraction over the DOM, that certainly doesn't match any existing implementation and doesn't feel like a primitive.

I would argue it's more of a primitive than tightly coupling DOM mutations and layout, but also:

* By having a way to express a patch we encourage developers to think more carefully about DOM mutations and how to go about them.
* It enables developers to send all UI input directly to workers and work on new views there.
* We could allow these patches to be reused, even have them accept parameters, to make tree building simpler and even more encourage this kind of grouping.

Creating a patch is also a pattern that all major frameworks seem to have converged on. Some as the result of diffing, others through slightly different techniques. It definitely feels like a primitive worth having to me.

(@drufball, you might want to open separate issues for the other proposals. That should at least inform everyone following the development of the DOM Standard where it might go next.)

---
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-227731628

Received on Wednesday, 22 June 2016 12:46:39 UTC