The reference-vs-value from elewa-academy

reference-vs-value's Introduction

Storing by Reference vs. Value

"Object" is a confusing word in JS. It can have two different meanings:
1. Anything that isn't a primitive (arrays, functions, objects. for now). This is because of how JavaScript handles inheritance and types behind the scenes. Take our word for it right now, you'll learn how it works later on.
2. The data structure defined by curly braces: {property: "value"};
Primitives vs Objects
Storing by value:
- Variables that are assigned primitive values directly store a copy of that value.
- Modifying a variable's primitive value does not effect memory anywhere else in the program.
Storing by reference:
- Variables that are assigned object values (functions, arrays, objects) do not store their own copy of that object. They store a pointer to where that object lives in memory.
- Modifying a variable that points to an object will immediately effect any other variable pointing to that same object.
Side Effects: When making a change to one piece of your program causes changes somewhere else. We see this with the two variables reference_1 and reference_2.
Garbage collecting. If no variables are pointing to an object in memory, that object is un-reachable and will be deleted from memory.

The Code

let value_1 = 5;
let reference_1 = [];

let value_2 = value_1;
let reference_2 = reference_1;

value_2++;
reference_2.push(value_2);
console.log(reference_1);

reference_1 = null;
reference_2 = null;