@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
@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
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:
Someone was like "they're building a dream team with Lea, Cory and Zach"
And never have I felt this level of imposter syndrome...
@polotek @slightlyoff NextJS is closer in relation to Angular and Ember in that both projects ship SSR, routers, etc
It's definitely not apples to apples with React to Angular
@polotek @slightlyoff oh there's also NextJS which last I checked was like 87kb , but probably getting bigger.
@polotek @slightlyoff Theres also EmberJS at ~140kb gzipped.
@polotek @slightlyoff Looks like somewhere around 60kb
@scottjehl Literally the most annoying thing. I'll happily pull your fonts from the CDN, but give me the damn font face rules!
@zachleat only way to cure the brain worms
@zkat IIRC big things are loading, iframes loading is like the lowest thing in the fetch priority queue and rendering queue, the fact iframes don't auto grow to the size of content is obnoxious. Screen readers are pretty fine with iframes. As a whole they're not bad, they just have some annoying pieces that make things slightly worse than just using your existing page.
@slightlyoff and versions if applicable!