The condition of the loop does not dictate when the loop stops, it dictates when the loop should continue. counter == 100 says "only loop when counter is equal to 100", but you're expecting the opposite to happen. In this option, the counter should stop when the value 100 would be attributed to the counter (note the "="). No, because = doesn't check for anything. = is assignment. It's setting counter to be 100 every iteration, then evaluating to that 100 value, and 100 is truthy so the loop never ends. More on reddit.com

Good morning, I am a little confused on the logic of a for loop. If you have to find the min and max number of an array how would a for loop be used to iterate through the loop in a function? Here is example code for max number. ----- .sort() is not allowed to be used. function max(numbers) ... More on forum.freecodecamp.org

Coding is hard, that's why not a lot of people do it. So I can assure you that this, you struggling, is going to happen again. You have to be ok with not fully understanding everything, mainly because you don't need to, to be a successful programmer. More on reddit.com

Some differences include: for loops for (let i = 0; i < arr.length; i++) { // loop code } User defined loop conditions Allows breaking (and continuing) Supports await/yield for surrounding scope Standard usage for arrays gives you index only, not value Tends to be more complicated than other loops (less readable, more error prone) But also most flexible in how looping is defined for of loops for (const element of arr) { // loop code } Loops through iterables only Allows breaking (and continuing) Supports await/yield for surrounding scope Standard usage for arrays gives you value only, not index Other helpers needed for specific kinds of iteration, like array.entries() to get indices and values, or Object.keys() for going through keys of objects For arrays, loops through all values, even holes when arrays are sparse for in loops for (const key in obj) { // loop code } Loops through any value Iterates through value keys, both own and inherited (Object.keys(), by comparison, only provides own keys, not inherited) Allows breaking (and continuing) Supports await/yield for surrounding scope For arrays does not include holes when arrays are sparse (not recommended for looping through arrays) forEach loops arr.forEach(function (element, index, arr) { // loop code }) Only usable for collections that have this method (arrays, typed arrays, and some others like NodeLists from DOM API) Uses a callback function rather than looping through a code block Does not allow breaking Does not support await/yield for surrounding scope (though you can await and yield in the callback itself, it doesn't affect the looping) Gives you value, index, and collection being looped for each iteration For arrays does not include holes when arrays are sparse Often considered the most readable, especially when reusing callback functions (arr.forEach(doThing)) though can also be least performant More on reddit.com