Question

In the last couple of months, I’ve been learning a lot about JavaScript. Having abused the languages for years, I dare say that I now have a better understanding of the language and I’ve come to love the benefits of its functional nature.

Lately I’ve taken up learning Scheme, but that’s just for fun. Browsing the MDN reference I noticed that JS, though lacking block scope, does have a keyword that can be used to declare a variable local to a given block, much like Scheme’s let:

for (var i=0;i<someArray.length;i++)
{
    console.log(someArray[i]);
}
console.log(i);//will log someArray's length

Whereas:

for (let i=0;i<someArray.length;i++)
{
    console.log(someArray[i]);
}
console.log(i);//undefined

So what I want to know now is: Why isn’t let used more often? Has it got something to do with X-browser support? Is it just one of those lesser-known-goodies?
In short, what are the advantages of using var over let, what are the caveats?

As far as I can tell, the behaviour of let is, if anything, more consistent (double declarations in a single block raise a TypeError, except for function bodies (ECMA6 drafts fix this, though).
To be honest, apart from this feature/keyword not being very well known, I struggle to think of any argument against using let for loops, or anywhere where a temporary variable makes for more readable code.

Answer 1

Yes, it has entirely to do with browser support. Currently only Firefox implements it (since it’s part of their superset of ECMAScript).

But it is coming in ES6, so there’s hope…

I doubt it could be said that there are many benefits to var over let given that both are supported. I think the mantra is going to be “let is the new var“