As is becoming traditional at this point, I'm here for questions if anyone has them. I work on Chakra (and, it goes without saying, am realllllly excited about this announcement)!
Because of the rapid progress in js engines, it's always difficult to keep track of what can can't be optimised. What are some big things to look out for in performance sensitive code to stop deoptimisation, and are there any things to consider to get better performance when you know an area of code is a bottle neck?
JITs are pretty complicated so it's hard to give a concise answer for what to use or avoid. This is an area I hope we can start giving more insight on in terms of both documentation and tooling.
75
u/bterlson_ @bterlson Dec 05 '15
As is becoming traditional at this point, I'm here for questions if anyone has them. I work on Chakra (and, it goes without saying, am realllllly excited about this announcement)!