It amazes me how doing something as simple as making sure your objects have the same shape, even if it is empty, can make a significant impact on performance. Excellent presentation, I think I will have to to a look at some code and see if I can make some improvements to some code I have been working with lately.
is the property lookup not constant time when accessed for the first time? (probably yes because we have to traverse the transition states of shape object) since there are offsets in the property metadata, it means that there is an inherent ordering in the properties.. i.e. for object {x: 1, y: 2, z: 3} - we will have x at offset 0, y at offset 1, and z at offset 2. But now if we have an object {y: 1, z: 2, x: 3} - does this share the same shape transition tree or is it different?
Okay but how does it kill the kitten and how do we know if it kills an entire kitten family or not this I don't get 🤔 If the array has 1 index it kills 1 kitten and if it has more than 1 it kills a family?
Can we (only for fun) do all that stuff that we should not do in JavaScript (without killing a kitten) in a kind of fantasy land (not related to functional programming just using same name to describe something else)
![Mathias B, Benedikt M - JS Engine fundamentals [AgentConf]](http://i.ytimg.com/vi/0I0d8LkDqyc/mqdefault.jpg)
This talk is superb. Mathias and Benedikt are the best teachers when it comes to demystifying the complex topic.
This fabulous comedy duo can be seen on tour with Wanda Sykes with their pre-show JIT Comedy performance. Love your work, boys. Keep it up.
Your explanation of inline caching was amazing! Thank you for this gem!
Awesome talk, thanks!
Very cool small look into engine optimizations
Excellent presentation style! No need to mention content!
It amazes me how doing something as simple as making sure your objects have the same shape, even if it is empty, can make a significant impact on performance. Excellent presentation, I think I will have to to a look at some code and see if I can make some improvements to some code I have been working with lately.
great visuals, keep up the good work guys!
is the property lookup not constant time when accessed for the first time? (probably yes because we have to traverse the transition states of shape object)
since there are offsets in the property metadata, it means that there is an inherent ordering in the properties.. i.e. for object {x: 1, y: 2, z: 3} - we will have x at offset 0, y at offset 1, and z at offset 2. But now if we have an object {y: 1, z: 2, x: 3} - does this share the same shape transition tree or is it different?
Is the Chromium based Edge is using Chakra or V8 ?
what data structure do they use to store shapes and actual values???
This is gold
Nice. Thanks!
Never miss a mathias conference hehehe
really nice talk!!
wow this is so informative
Okay but how does it kill the kitten and how do we know if it kills an entire kitten family or not this I don't get 🤔
If the array has 1 index it kills 1 kitten and if it has more than 1 it kills a family?
excellent!
Great!
Thx!
Can we (only for fun) do all that stuff that we should not do in JavaScript (without killing a kitten) in a kind of fantasy land (not related to functional programming just using same name to describe something else)
The JavaScript language is a kitten killer
👍