** UnhandledExceptionEventHandler :: OFFICIAL LC / CHATTER THREAD **
01-02-2018
, 04:24 PM
01-02-2018
, 07:03 PM
Yea, I basically just avoid all of that. I also wanted to ask if people ever use the "new" keyword? I find it kinda weird and ugly, and would think any code I'm looking at that uses it is likely ancient, and proceed cautiously, is that wrong?
Also, today I was "giving back" to the bootcamp I attended and doing some mock interviews with people in a class. I asked this question:
And someone came to me during their lunch and asked about it specifically. I pulled up a couple websites and walked them through the official explanations of how objects are passed by reference, and I saw that "null" is pass by value. But I know that the typeOf(null) is an object because of the original implementation. So I explained the null thing quickly, but I was taken aback at trying to teach a simple concept to someone needing to have that quirk explained. How this wasn't corrected early on really blew my mind.
I also found this:
That's obviously completely wrong right? If you pass an object as a function argument, you are referencing the same object in memory inside that function, so if you make changes to it, then you'll be changing the original object as well. This is like the whole reason for stuff like immutable.js right?
Also, today I was "giving back" to the bootcamp I attended and doing some mock interviews with people in a class. I asked this question:
Code:
let myObj = {
name: "david",
id: 5
};
let myStr = "ben";
let myNum = 5;
let myBool = true;
const x = function (obj, str, num, bool) {
obj.name = "john";
str = "donald";
num = 10;
bool = false;
}
x(myObj, myStr, myNum, myBool)
console.log(myObj, myStr, myNum, myBool)
// what will be logged?
I also found this:
That's obviously completely wrong right? If you pass an object as a function argument, you are referencing the same object in memory inside that function, so if you make changes to it, then you'll be changing the original object as well. This is like the whole reason for stuff like immutable.js right?
01-02-2018
, 07:18 PM
use new for 2 things: new Date(), and making an empty array of foo size usually so you can do the bastardized version of range i.e. const range10 = new Array(10).fill(true).map((el, i) => i)
don't use const for objects or arrays unless you're actually reassigning them.
don't use the function keyword ever other than exports.
10 seconds in console proves it passes by reference btw dunno what that article's about.
01-02-2018
, 08:32 PM
01-02-2018
, 08:48 PM
01-03-2018
, 12:18 AM
Two months too late oh well.
01-05-2018
, 02:38 PM