Re: [whatwg/dom] Model -> View (DOM el) reactivity (Issue #1049)

Seeing as though I have to be in the same area as you, and live with you it’s not going to work cuz I can’t be there 


Sent from Yahoo Mail for iPhone


On Monday, January 31, 2022, 1:39 PM, Darien Maillet Valentine ***@***.***> wrote:





I haven't seen any work done on it in a long time, but the DOM parts proposal was supposed to provide access into areas of DOM such that content could be updated fairly directly.


@Jamesernator that’s what I was thinking of, earlier. I’d thought I’d see relatively threads on it but maybe I was reading older stuff than I realized. It seemed like a pretty strong starting point at the least, so seems a bit sad to hear it’s not moving.


Many web apps (that are using a certain library/framework) use a model->view pattern, as it best describes the intention, and I think having a descriptive functionality is needed so people won't have to reinvent the wheel with every library, but use the standards provided by the runtime.


I think that makes sense, too. I suppose I think the work to get there mostly lives in a different place, but I don’t mean to discourage the investigation or anything.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>





-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/dom/issues/1049#issuecomment-1026375813

You are receiving this because you are subscribed to this thread.

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