@_developit I'm curious, what's your take on fiber, and what it means for Preact? (Sorry, I realise you're probably sick of this question)
-
-
Replying to @markdalgleish
not sick of it at all! I'm more ashamed to know as little as I do about fiber. From what I understand, it's rly a few things
1 reply 0 retweets 1 like -
Replying to @_developit @markdalgleish
first, the renderer seems to be modified to support serializable units of work, which is neat. not sure the use-case but neat
3 replies 0 retweets 1 like -
Replying to @_developit @markdalgleish
then there are a few key new features they are adding like fragments, which I actually find to be an unnecessary feature
2 replies 0 retweets 1 like -
Replying to @_developit @markdalgleish
the end result seems to produce something fairly similar to
@aerotwist's PR though, which gives control over async rendering1 reply 0 retweets 1 like -
that part I do see huge value in, and I'm thrilled to be looking into it for Preact thanks to Paul's awesome idea.
1 reply 0 retweets 1 like -
Replying to @_developit @markdalgleish
I’m taking all the credit here. And for Preact as well… why not? I mean, I didn’t write any of the code. Whatevs.
1 reply 0 retweets 3 likes -
Replying to @aerotwist @_developit
I'm that case, love your work Paul, Preact looks great
1 reply 0 retweets 4 likes -
-
: I'm similarly confused re: fiber. See mountComponent storms; work smearing a bucket once you're sunk?
-
-
that's sortof my source of confusion. It's cool to have the ability to manage work, but... overhead?
1 reply 0 retweets 1 like - 18 more replies
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.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.
