var vs let vs const: Not Syntax, It’s About Behavior

A classic JavaScript interview question:

“What’s the difference between var, let, and const?”

Typical answers:

• var is old

• let/const are new

• const cannot change

But that’s not the real answer.

The real question is:
🐜 Do you understand how your code behaves?

Think simple

When you declare a variable, you're deciding:

• where can I use this?

• how can it change?

That’s where var, let, and const differ.

Scope (this is the real deal)

if (true) {
  var a = 10;
  let b = 20;
}

console.log(a); // 10
console.log(b); // error

• var → “I’m everywhere”

• let/const → “I stay here”

🐜 one is uncontrolled
🐜 the other is predictable

Hoisting (properly understood)

console.log(a); // undefined
var a = 5;

console.log(b); // error
let b = 5;

• var → exists but empty

• let/const → not accessible yet

TDZ

{
  console.log(x); // error
  let x = 10;
}

It simply says:

🐜 don’t use it before defining it

This prevents bugs.

const is misunderstood

const user = { name: "Ali" };
user.name = "Veli"; // works

const does NOT freeze values.
It freezes the reference.

Why var is dangerous

var a = 1;
var a = 2; // allowed

That’s not flexibility.
That’s risk.

Real-world bug

for (var i = 0; i < 3; i++) {
  setTimeout(() => console.log(i), 100);
}
// 3 3 3

for (let i = 0; i < 3; i++) {
  setTimeout(() => console.log(i), 100);
}
// 0 1 2

If you don’t understand this:

🐜 you will ship bugs

What to use?

• default → const

• changing → let

• avoid → var

Lazy Ant perspective

This is not about keywords.

It’s about:

🐜 how predictable your code is

Good systems:

• don’t surprise you

• have clear boundaries

• behave consistently

Conclusion

This looks like a small detail.

But:

• scope bugs

• async issues

• unexpected behavior

often start here.

It’s not about syntax.
It’s about control.

And good engineering is about building systems you can control.