Re: [whatwg/dom] Basic DOM reactivity (Issue #1049)

Thanks @bathos for the detailed comment, I do try to refine the idea:

I'm not suggesting a new feature that will introduce a new capability that can not be solved with a workaround, my idea is to have some primitive function that allows reactive DOM change based on an object mutation (or something on this direction).
The reason for it is that almost every reactive library (react, vue, svelte, solidjs...) are based on the fundamental idea of having a declarative code that says "when this value changes, the view should change with the value", so I thought why not having it "baked in" the DOM API, or at least a primitive version of it (of course there is always a room for libraries to provide more abstraction, but having a DOM function that updates the element's content/attribute when data changes can push those technologies forward)

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

Message ID: <whatwg/dom/issues/1049/1022158399@github.com>