I think that's probably true, but it's not inherent. "I have this state lying around" is a good way to lock into hard-to-optz APIs.
1: https://twitter.com/dan_abramov/status/921165636151271424 … The question here is what is a "functional component". Glimmer VMs perspective is:
-
-
2: these hooks are all capabilities. We compile a hook invocation if a component declares that it uses that capability.
-
3: so a functional component (a "template only component" in glimmer) is a component that uses very minimal capabilities.
-
4: this makes the curve from "full featured expensive component" to "pure functional component" more graded.
-
5: a "class-based Component" can have fewer hooks, and a "functional component" can implement the dynamic features via params.
-
6/6: that's the low level. At a high level the conveniences are more coarse obv.
End of conversation
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.
Locked in to the cWRP API with old + new props, assuming that there's unwanted overhead there