JavaScript Scope Chains and Closures

[@nooxis]

Really one of the best explanations of JS scope and closure I have seen.

[@roychoo]

大悲咒

[@riclf]

Very well explained. I also appreciate that your voice as a presenter was clear and strong. Really helped.

[@oohkumar]

Still one of the best explanations of closures after all these years.

[@kozmicluis2552]

Probably the best explanation of scope and hoisting I've ever seen.

[@awc032]

Thank you Adam. We need more wonderful JS teacher like yourself. Please keep publishing your talks!

[@prashantagarwal3339]

you are the best teacher i have encountered in my entire life....thank you very much adam... :)

[@aBamieh]

you have not encountered enough teachers then. he did a good job, but far from the best in my opinion.

[@josealfonso2117]

Dude! This is the best presentation about Javascript I've seen in a while. It comes to prove that when you know what you are talking about you can explain it in simple terms! - Thanks! :-)

[@art123-c4r]

Thanks! It's been very interesting and first of all really compelling while you watching. Love the way how this guy conveys the information to the audience.

[@JohnDoe-op2lr]

Great explanation. Even though I kinda suspected some of this before the video, this video really put everything in it's place. Thank you very much.

[@linardzb]

very interesting presentation, any plan to make one on functions and methods?

[@cupajoesir]

Nicely framed and good context provided. Thanks for posting.

[@estefaniakiara-elizabeth8538]

Thank you!!! great explanation, I was confused about scope and closures but your presentation clarified my questions and doubts.

[@JoffreyKanmogne]

Great! I understood a bunch of things on scopes chain, closures and hoisting

[@maurocremonini]

Thank you very much for this outstanding presentation. Very clear!

[@SachinSingh-qe1dg]

Really one of the best explanations.. loved it..

[@TheHolyReality]

Great video. The only thing that left me confused was in the last few minutes of the video. When you showed that you can see private data using Chrome developer tools (using console.dir) through Function scope tree. Does this mean that anyone can *see* what the private data is even tho they cant do anything with it?

[@tarunpahuja3443]

Could you please tell how scope chain would look like for "module pattern .." examples. Please

[@santosharakere]

Excellent Presentation. Thank you.

[@api-first]

This is such an amazing video!

[@cupajoesir]

It was mentioned that these slides were on speaker deck. Is there a link?

[@SmartWizzard]

Hi, where can I download these slides. I they very resourceful for reference.

[@syedali-le6ii]

What is the difference between Lexical Scoping and In-Memory Scope?

[@gamingcroctv4523]

AHA moments! thanks for this!

[@LeBadman]

Excellent explanation!

[@NathanComstock-sf]

[@MrinmoyRoy1990]

Excellent! Just Excellent!

[@itsdannyftw]

Wait, so scope chaining (the black arrows) is only possible due to the [[scope]] member? Don't think he explicitly stated this so could anyone please confirm? Otherwise my question was how do those black arrows know where to point to, etc? Is there some other back-end mechanism? or is it just because of [[scope]]?

[@Oscar-mp6hw]

Great Job! Thank you for making it easier. Subscribed.

[@niktwister]

Can anybody explain how "let" and "const" will fit into all this ? I mean how block scopes are handled ??

[@nadavgampel6585]

where can I find the notes of this lecture ?

[@0xO2]

Isn't that local scope also has slot/name of the own declared function (to make recursion work)? ``` > var G = function B() { console.log(B) }; undefined > G() VM7249:2 function B() { console.log(B) } undefined > B() VM7292:2 Uncaught ReferenceError: B is not defined(…) ``` while such case may seem like *g* is in outer scope ``` > (function g() { console.log(g) })() function g() { console.log(g) } ``` Or there is another [[magic]]?

[@subhashgn1775]

Arindam paul in the audience.....

[@stevend1752]

Thank you, finally I fond the answer :)

[@MohamedHamed-oz6nq]

best of the best

[@HuaJarry]

THANKS A LOT.

[@mikhoq]

Magically disappears at 53:53

[@syzer3921]

1 person missed the like button :)

[@AjinkyaBorade]

it could have been more interesting if the speaker could show more practice examples, theory bores me

[@wjrasmussen666]

Yes, having it fully explain is often better for people who need to learn something new.

[@MarioCarrizalesArt]

great info just too much repetition of "um...", "so um..." really annoying. I did click the "LIKE" button.

[@lgiccambodia]

Not fast enough get bored

[@cupajoesir]

settings->speed->2.0 you're welcome.

[@aBamieh]

This guy heavily takes from Kyle simpson and philip roberts. if youre new to this, check them out they did a far better job at explaining these concepts. and wow thats in 2014 and JS programmers dont know what and IIFE is? Amateurs detected!

[@TheHolyReality]

Are you experienced well with Javascript? I would like to ask you a quick question just to clarify things.

[@aBamieh]

i believe so, sure go ahead

[@TheHolyReality]

Ahmad Bamieh In the video, he showed how he can access private data using console.dir and then look it up in Function scope property. Does this mean that anyone can see any private data that we make using this simple method in Dev tools,even tho they cant manipulate it in any way? I mean it seems to me that its a security flaw for anyone even to see the private data.