I assume it's about fiber?
-
-
-
Replying to @sebmarkbage
I've heard whispers of some pretty significant improvements in practice.
1 reply 0 retweets 0 likes -
Replying to @wycats
Unfortunately many people also have the wrong idea of what it does. It's not magic but I like the trajectory.
1 reply 0 retweets 1 like -
Replying to @sebmarkbage
is it more than allowing more smearing of the rendering task? (i.e. improvement in jank but not total time)
2 replies 0 retweets 0 likes -
Replying to @wycats @sebmarkbage
or does it also have additional wins (maybe GC semantics?)
1 reply 0 retweets 0 likes -
Replying to @wycats
It does but those haven't been at the scale that they're relevant for any of our use cases yet.
1 reply 0 retweets 0 likes -
Replying to @sebmarkbage
sounds about right. I think the smearing is a pretty important unlock. Excited to see where you take it.
2 replies 0 retweets 2 likes -
Replying to @wycats @sebmarkbage
it also firmly goes beyond what a naive implementation of
#UseThePlatform could plausibly do. That argument's on its deathbed.1 reply 0 retweets 8 likes -
Replying to @wycats
The platform could implement similar hooks though so excited about new ideas it might spawn for standards.
2 replies 0 retweets 2 likes
but people would have to enqueue entire DOM jobs, which we could use in frameworks but would be implausible for naive code.
-
-
Replying to @wycats @sebmarkbage
DOMChangeList was extracted from similar ideas in Ember/Glimmer and I'd love to chat about that sometime.
1 reply 0 retweets 2 likes -
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.