Re: [WICG/webcomponents] Idea: A tree-aware task scheduler (Issue #1055)

noamr left a comment (WICG/webcomponents#1055)

This enables a very particular low-level JS-based hook for frameworks, kind of like DOM parts and other proposals.
These low level solutions seem to be designed for a particular generation of a particular architecture, and IMO won't help push the platform forward. 

More over, developing something like this as a web standard is quite complex, and the only way for that to be justified would be to show a very measurable performance gain in multiple situations, which we'll only know after quite a bit of work. Even after doing so, it won't be clear if the solution is useful for the next iteration of whatever frameworks come up with.

I would very much prefer to address DOM scheduling issues on the HTML level in a way that can be used declaratively (e.g. declaring a batch of changes that don't allow rendering in between or some such) rather than as a low level library hook.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/WICG/webcomponents/issues/1055#issuecomment-4508813680
You are receiving this because you are subscribed to this thread.

Message ID: <WICG/webcomponents/issues/1055/4508813680@github.com>