The inability to statically analyze a ton of popular JavaScript patterns makes a lot of *really* cool things infeasible for broad adoption. Requiring some rules/conventions gets you some of the way there, but still a big bummer.
-
-
Replying to @_jayphelps
What are some examples of JS patterns you'd ideally like to analyze?
3 replies 0 retweets 2 likes -
Replying to @DavidKPiano
React components completely break down without first-class knowledge of how React works built into the processing.
2 replies 0 retweets 2 likes -
Replying to @_jayphelps @DavidKPiano
I guess "completely" might be too definitive. I personally haven't been able to make it work, with many things the internals of React do. Not in *any way* implying they shouldn't do what they do, just because of the lack of type system has made it impossible, for me.
2 replies 0 retweets 0 likes -
Replying to @_jayphelps @DavidKPiano
I'm not sure if Prepack built-in React heuristics or figured it out. It is (was?) pretty complex after all.
1 reply 0 retweets 0 likes
Replying to @_jayphelps @DavidKPiano
It built it in.
11:38 AM - 25 Mar 2020
0 replies
0 retweets
1 like
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.
he/him 