Right - not very common, like he said :)
-
-
Agreed, but backwards compat was a goal for 16 w/ Fiber so it was already ~locked in, maybe that could change if a better API is proposed
-
Functional components don't have hooks. How is cWRP discussion relevant to functional components? What lock in are we talking about?
-
This part wasn't about functional components
Locked in to the cWRP API with old + new props, assuming that there's unwanted overhead there -
Which I'm saying I don't *think* there's really overhead because we already have old + new props at this point for other reasons
-
but even if there *was* overhead that *was* unwanted, backwards compat means keeping current + new for cWRP since that's the current API
-
This conversation has kinda gone down hill. It started by comparing glimmer and react arch. I was giving a reason glimmer doesn't like this.
-
There's otherwise a lot of equivalence between the APIs and I said I don't think there are good use cases for these hooks.
-
So I was kinda teasing out differences between the implementations and community norms.
- 7 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.