Franziska Hinkelmann: JavaScript engines – how do they even? | JSConf EU 2017




http://2017.jsconf.eu/speakers/franziska-hinkelmann-javascript-engines-how-do-they-even.html

Want to know how JavaScript engines work? Why is JavaScript so fast? What is just-in-time compilation? We’ll look at basic concepts of compilers, challenges posed by modern JavaScript, and how to write compiler-friendly JavaScript.

Original source


28 responses to “Franziska Hinkelmann: JavaScript engines – how do they even? | JSConf EU 2017”

  1. Sehr interessant, Dankeschön!

    Would you agree that the statement "From a compiler's perspective, the best thing we can do is to write code that looks like it is statically typed", can be used as an argument in favour of TypeScript, which as I understand it naturally encourages us to write code that looks like it is statically typed. Hence, does writing our code using TypeScript make it more likely that the resulting JavaScript code can be optimised in a way that increases performance?

    Using that argument, can it therefore be inferred that "using TypeScript makes our apps faster"?

  2. C++ has 'auto' which works similar to 'var' in Js. But, exactly as in Js, you cannot ignore the type. Even assignment does different things, depending on the type of the variable. In Js, primitives will be copied but objects will be a copy of reference, which then refers to the same object.

  3. Thanks for the presentation. I'm in a bit over my head, but I was able to follow along. I am uncertain about one point, though.

    Given two objects {x:"a string", y:5} and {x:"another string", y:7}, would they be of the same type, despite differing string lengths? Is the string value of obj.x stored by reference so that the location of obj.y is always the same, relative to the object?

Leave a Reply