Perhaps I was not quite the target audience for this talk. I found the pace pretty quickly outdistanced my foundation of JS. As a result, at least I was introduced to concepts that may help improve my JSing, but I found myself struggling to understand the before and after picture of object literal vs ... what ... function as class?
Thanks for the feedback anonymous (both of you)! Perhaps I need to do a better job at identifying the target audience in the abstract and what might be good to know beforehand.
To your confusion: you're right, coming from a classical inheritance model can cause confusion when one tries to draw parallels. Instead, I would recommend trying to ignore what you know about OOP in classical systems and instead try to learn prototypical inheritance with "fresh" eyes! In others words, don't try to understand that a "class" is in JavaScript, but rather, try to understand what a "prototype" is.
I don't have the background to get the most out of this talk, but I enjoyed hearing about OO JavaScript. I would like to use the slides to guide me in a self-study to gain a better understanding. The speaker obviously understood the material.
I have only been dealing with OO Javascript (ExtJS) for the past year without understanding how it was OOP nor why we did things the way we did. I just followed the example provided by my team while I was trying to figure out the whys and the wherefores.
This talk helped me understand more about what I was doing in JavaScript than the various books I've read in the attempt to do so.
Comments
Comments are closed.
High energy, highly useful. Tied in a bunch of ideas into context do that my understanding is much improved
This was fantastic, and certainly one of my favorite today. The presentation quality was excellent, and I learned a lot.
Very, very well done! I appreciate the effort and the clean humor through the talk. Thank you!
Perhaps I was not quite the target audience for this talk. I found the pace pretty quickly outdistanced my foundation of JS. As a result, at least I was introduced to concepts that may help improve my JSing, but I found myself struggling to understand the before and after picture of object literal vs ... what ... function as class?
Thanks for the feedback anonymous (both of you)! Perhaps I need to do a better job at identifying the target audience in the abstract and what might be good to know beforehand.
To your confusion: you're right, coming from a classical inheritance model can cause confusion when one tries to draw parallels. Instead, I would recommend trying to ignore what you know about OOP in classical systems and instead try to learn prototypical inheritance with "fresh" eyes! In others words, don't try to understand that a "class" is in JavaScript, but rather, try to understand what a "prototype" is.
awesome talk. would've liked to see sample code from the JS OO frameworks. i'm glad i went because now i know that i've been living a jQuery lie
Energetic and knowledgeable speaker. High quality presentation. Good stress on the fundamentals/concepts.
I don't have the background to get the most out of this talk, but I enjoyed hearing about OO JavaScript. I would like to use the slides to guide me in a self-study to gain a better understanding. The speaker obviously understood the material.
I have only been dealing with OO Javascript (ExtJS) for the past year without understanding how it was OOP nor why we did things the way we did. I just followed the example provided by my team while I was trying to figure out the whys and the wherefores.
This talk helped me understand more about what I was doing in JavaScript than the various books I've read in the attempt to do so.