he/him 
I'll be writing an explanation of what's going on and why it's significant/what practical learnings we can gain from this. ... I'm still evaluating it myself...
Show this thread
-
Babel thing also shifted work to be eager which isn't ideal. Ideally it'd be lazy first time it's rendered.
Makes so much sense now, but I've never noticed this until now 
Are we referring to the constant elements transform? It just hoisted the React.createElement calls. Wouldn’t they just be creating the element objects eagerly? What other work would it be doing?
-
-
Yea. Not so much buggy but I think surprised people. Moving to module level resulted in more start-up costs even if a component wasn't rendered. I'm guessing the ideal state might be closer to memoized after first use.
-
Maybe there’s a better case for hoisting now that we have React.lazy?
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.