Made a video of "The 2 client problem", the first time I heard a term coined for "2 independent lifecycle managers fighting for control of markup + state" and showing how DOM Diffing shows up with web components and why light dom web components (HTML ...
-
Made a video of "The 2 client problem", the first time I heard a term coined for "2 independent lifecycle managers fighting for control of markup + state" and showing how DOM Diffing shows up with web components and why light dom web components (HTML web components) are really difficult to share with frontend frameworks.
I believe I first heard the term from @jaffathecake
anyways, heres a video of the problem:
-
Zach Leatherman :11ty:replied to Konnor Rogers last edited by [email protected]
@konnorrogers @jaffathecake For the @eleventy dev server (in v2.0.4), we’re experimenting with reattaching custom elements when the nodes are updated to workaround this issue https://github.com/11ty/eleventy-dev-server/commit/c7ead8e3488eed7343bb26b11d1054d5b8233433
-
Konnor Rogersreplied to Zach Leatherman :11ty: last edited by
@zachleat @jaffathecake @eleventy Its a legitimately hard problem
and this doesn't even touch on people wanting to "hot module replace" components.
im not gonna sit here and pretend shadow dom is perfect either.
its just another example of tradeoffs
-
Zach Leatherman :11ty:replied to Konnor Rogers last edited by
@konnorrogers @jaffathecake @eleventy seems worth naming! first I’ve heard this name