I'm not fully convinced by that video Dice, I didn't watch much past the looking up of JS. First off as far as I remember, that setTimeout method he's referring too he has incorrectly inferred it's usage and while he could still be correct, again not having gone through the whole thing, he never explored the inner laying functions JS was calling.
The 5E3 parameter(weird, I've never seen it written in scientific notation, only as whole number, ie 5000)being used is a delay, however that delay is issued AFTER that set time. It is NOT running immediately. So the functions inside run after the delay. Seeing as the video starts and is then refreshed immediately, I'm not seeing pure evidence based off the small snippets he showed.
I could be wrong but we need more information than what's shown here to make a conclusion. Finding one setTimeout function is not evidence of much considering that massive code shown in the video.
The only way I see it as true, is he got it all wrong at face value, but is correct in that after initial loading, a different function is kicking in that cause the weird issues, after the setTimeout parameter is met and refreshes the page. How YouTube tracks the number of refreshes before stopping the functions I did not see in the video.
Hope that makes sense. I posted this in a hurry.
