7:24 Boolean is treated as 0 or 1 when added to a number. Whenever bool or number is added to string their respective toString conversion is used ('true' 'false' for bool.) What's odd is that if("") and if(0) don't evaluate to false. 9:00 interfaces sure can help bring down the size of parameters 10:45 optional always has to be at the end I assume 12:24 Interesting. In a way JavaScript by default is infinitely overloaded as it doesn't care what you put in for parameters!) 21:00 Does it have to encapsulate the function within 2 pairs of parenthesis? (closure access to an outer scope from an inner 22:15 If the parameters were say x1 y1 then I think you wouldn't need to use 'this' to differentiate from inner to outer scope. 25:30 Once you compile C/C++ private vars are just the same as public, it's only in source code that is has any meaning. TypeScript could be thought as source, JS as compiled.
Now with Channel 9 dead, yours is the only copy of this video remaining on the Internet. Thank you for this.
7:24 Boolean is treated as 0 or 1 when added to a number. Whenever bool or number is added to string their respective toString conversion is used ('true' 'false' for bool.) What's odd is that if("") and if(0) don't evaluate to false.
9:00 interfaces sure can help bring down the size of parameters
10:45 optional always has to be at the end I assume
12:24 Interesting. In a way JavaScript by default is infinitely overloaded as it doesn't care what you put in for parameters!)
21:00 Does it have to encapsulate the function within 2 pairs of parenthesis? (closure access to an outer scope from an inner
22:15 If the parameters were say x1 y1 then I think you wouldn't need to use 'this' to differentiate from inner to outer scope.
25:30 Once you compile C/C++ private vars are just the same as public, it's only in source code that is has any meaning. TypeScript could be thought as source, JS as compiled.
Thank you!
Excellent talk !!