Crockford on JavaScript - Chapter 2: And Then There Was JavaScript
Why Stack Overflow recommends it
Stack Overflow users link it when answering questions about JavaScript fundamentals such as prototypal inheritance, scope, and why the language behaves the way it does.
Recommended by 2 people across 2 different months, 2012 to 2014.
What it is
Douglas Crockford, then Yahoo!'s JavaScript architect, gives a roughly 90 minute lecture surveying the features of the JavaScript language. It is chapter 2 of his Crockford on JavaScript series, covering the language's design, prototypal inheritance, and its good and bad parts.
What people said
Strong rec GitaarLAB · 2012-08 · Stack Overflow · on ““var” variables, "this" variables and "global" variables - inside a JavaScript Constructor”
Yes, you understand it! As for the second part of the question, it is all about inheritance, just like the relation between (global) window and the functions defined in it's scope (think root). So everything you do not re-specify, will be looked up at the ancestor. This is a tremendous good video [this video] by Crockford, who explains it REALLY well.
Recommends Nick Hagianis · 2012-01 · Stack Overflow · on “Is it a good idea to use a switch with fallthrough to handle default arguments in Javascript?”
+1 There's probably a better way to accomplish what you're trying to do without using a switch statement. some info on good vs bad parts of javascript: [this video]
Recommends GitaarLAB · 2012-08 · Stack Overflow · on “What are the differences between to create a "classic" class in javascript and JSON notation?”
There are no classes in javascript, javascript is a prototypal language. There is no way to explain this faster than watching: Crockford on JavaScript - Chapter 2: And Then There Was JavaScript [this video] for a simple CORRECT explanation by the father of json (amongst other things). Good Luck!!
Recommends GitaarLAB · 2012-08 · Stack Overflow · on “JavaScript set data structure with logarithmic search time”
yep, see Crockford on JavaScript - Chapter 2: And Then There Was JavaScript [this video] , and you WILL understand. Something to keep in mind: if needed, you check (set/convert) type of value before you use/read it, not while declaring the value.
Cites Ebrahim Byagowi · 2014-12 · Stack Overflow · on “What's wrong with JavaScript's regular expression notation?”
Possibly messed up with slashes used for comments and division per this [LINK] or because "they should be one line with no white space or commentary inserted to it" per this [this video] .