The Secret Memory of JavaScript Functions That Nobody Talks About
My Institute Trainer Mr.Vijayaragavan sir dropped this code on my screen during our training session: function makeCounter() { let count = 0; return function () { count++; return count; }; } const ...
Source: DEV Community
My Institute Trainer Mr.Vijayaragavan sir dropped this code on my screen during our training session: function makeCounter() { let count = 0; return function () { count++; return count; }; } const counter = makeCounter(); console.log(counter()); // 1 console.log(counter()); // 2 console.log(counter()); // 3 "How does count still exist?" I asked. "The makeCounter function already finished running." He smiled. "That's the secret every JavaScript function carries." I had no idea what he meant. But that moment changed how I write JavaScript forever. Here's exactly what we'll cover: 🕰️ What JavaScript used to do before this concept existed (and why it was painful) 🧠 The "secret memory" that every function carries — explained simply 🎯 Beginner, Intermediate, and Pro level Q&A 🧩 An interactive quiz to test yourself at the end 1. Before the Secret — What JavaScript Developers Suffered Through Before JavaScript had this feature, developers faced one massive problem: data didn't survive.
