#falsy

ytvids is an array that has an amount of x entries. subytids is an empty array.

Basically what I wanted to do here is take ytvids and split it into multiple arrays with the defined length of 50 entries each. .splice is destructive, meaning it removes elements from the array permanently compared to it's sister method .slice, which only gives back the entries but doesn't take them out of the array

var array = ["A", "B", "C"]; console.log(array.slice(0, 2)); // => ["A", "B"] console.log(array); // => ["A", "B", "C"] console.log(array.splice(0, 2)); // => ["A", "B"] console.log(array); // => ["C"]

So what this loop is supposed to do is splice out up to 50 entries every time the code in the loop runs and add the new array to the subytids array. And the code runs because an array is considered a truthy value in JS. So it runs and it splices and it runs and it splices. But someday, the array will be empty and splicing only returns []. What I did not consider is that an empty array actually STILL counts as a truthy value. Meaning the loop does not stop. And it keeps pushing and pushing empty arrays coming from .splice to subytids. Up to the point that there is just too much memory in the heap and it crashes.

What I ACTUALLY should have done in the first place, is use while (ytvids.length). Length is the number of items in an array and that counts down after each splicing. 0 in JS is considered a falsy value and breaks the loop when no more entries are remaining in the array.

There is only a handful of things that are considered falsy in JS, so you might want to remember those:

false (boolean)

null

undefined

0

NaN

'' or "" (empty strings)