This fried my brainhttps://twitter.com/ReactEurope/status/742366823203672064 …
-
-
Replying to @dan_abramov
This idea is super obvious in retrospect but I’d never come up with it. Something like this takes a feeling of real mastery over your tools.
1 reply 1 retweet 17 likes -
Replying to @dan_abramov
“I need to understand what this code is doing to compile it more efficiently. Why I don’t I build an interpreter so I know what it’s doing!”
3 replies 1 retweet 8 likes -
Replying to @dan_abramov
Also, v8 has had this built-in since last year: http://v8project.blogspot.com/2015/09/custom-startup-snapshots.html …
1 reply 0 retweets 1 like -
Replying to @timdorr
Yea, AFAIK not very helpful for websites though :-)
2 replies 0 retweets 0 likes -
Replying to @dan_abramov
Chrome has had a code cache for over a year: http://blog.chromium.org/2015/03/new-javascript-techniques-for-rapid.html …
1 reply 0 retweets 1 like -
Replying to @timdorr
This doesn’t save execution time from metaprogramming, just downloading/parsing/compiling
1 reply 0 retweets 0 likes -
Replying to @dan_abramov
v8 will identify hot paths and do further optimization itself. The code cache will keep those optimized versions.
1 reply 0 retweets 0 likes -
Replying to @timdorr @dan_abramov
This works in conjunction with a code cache. Initialisation code rarely benefits from JIT.
1 reply 0 retweets 3 likes
Even when JIT does matter, removing the initialisation entirely (which is what our compiler does) is faster.
-
-
Replying to @sebmck @dan_abramov
Ah, I see what you mean. I don't know if v8 tracks hot paths across inits (unlikely). Would be a good combo though!
0 replies 0 retweets 1 likeThanks. Twitter will use this to make your timeline better. UndoUndo
-
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 