• Monday , 25 May 2020

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

Code Canyon



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

3d Ocean

Related Posts

28 Comments

  1. srcmake
    June 10, 2019 at 18:55

    Amazing presentation. It explained everything really well and even taught me a few tricks.

  2. Snisser
    June 10, 2019 at 18:55

    17:16 "Plus 17"? Isn't that hexadecimal for 23?

  3. Hemant kumar singh
    June 10, 2019 at 18:55

    loved it…

  4. bouhannache abdallah
    June 10, 2019 at 18:55

    this course should one of the mandatory courses that a developer should follow to make the code work in very efficient way and give best performance and hardware management .

  5. Prashant Dhameja
    June 10, 2019 at 18:55

    Thanks a lot😄 this was a great video.

  6. Jay Sistar
    June 10, 2019 at 18:55

    Intro was a variation of Zelda fountian/file select music.

  7. Yash Choksi
    June 10, 2019 at 18:55

    Awesome explanation.

  8. Андрій Воробйов
    June 10, 2019 at 18:55

    Simple but useful presentation

  9. Felipe
    June 10, 2019 at 18:55

    Very nice … interesting …. I code while I listen …. nice

  10. Crab Synth
    June 10, 2019 at 18:55

    Awesome Presentation !!! This definitely Demystified some of the Inner workings of V8 for me. Kudos !

  11. Gautham B A
    June 10, 2019 at 18:55

    Very nice video. At 22:15, isn't the "let" keyword part of ES6 and not ES5?

  12. ben4d85
    June 10, 2019 at 18:55

    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"?

  13. Ron Isaac
    June 10, 2019 at 18:55

    I love listening to smart people.
    – thanks!!

  14. shubham agrawal
    June 10, 2019 at 18:55

    No wonder they names it V8, they made it in germany.

  15. Romain Vincent
    June 10, 2019 at 18:55

    The intro jingle is cool!

  16. szym
    June 10, 2019 at 18:55

    the first flag and the third flag does not work with chrome

  17. Oliver Ford
    June 10, 2019 at 18:55

    If websites provided v8 bytecode instead of js to skip parsing, how much quicker would it be?

  18. LuisMa Suárez Gutiérrez
    June 10, 2019 at 18:55

    is the intro supposed to sound like the zelda theme?

  19. manjeet kumar
    June 10, 2019 at 18:55

    I always likes experimenting with JS. And, this was pretty much informational for me.
    @Franziska Hinkelmann has blog about this. Check it for more info:

    https://medium.com/dailyjs/understanding-v8s-bytecode-317d46c94775

  20. mwm
    June 10, 2019 at 18:55

    Excellent talk. Thank you!

  21. Peter Barraud
    June 10, 2019 at 18:55

    Thanks much Franziska. Would love to see more of such stuff. Help us work better with the JavaScript engine

  22. Wobbly Bit
    June 10, 2019 at 18:55

    Why doesn't –print-opt-code work for me?

  23. Johannes Vollmer
    June 10, 2019 at 18:55

    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.

  24. Tobiasz Dziubiński
    June 10, 2019 at 18:55

    I'd love to study this in more depth. Anyone can recommend some book?

  25. MecchaKakkoii
    June 10, 2019 at 18:55

    Great talk.

  26. Matthijs Hebly
    June 10, 2019 at 18:55

    Started out a bit slow, but then this talk became very interesting indeed, and this will help us write better, faster code. Awesome!

  27. victornpb
    June 10, 2019 at 18:55

    will it help if you create constructors for obj insead of a literals? like function p(x,y){ this.x=x; this.y=y; } new p(1,2) then pass it to load(obj)?

  28. Mort Snoody
    June 10, 2019 at 18:55

    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 Comment

You must be logged in to post a comment.