undefined | Better HN

0 pointsheavenlyblue6y ago0 comments

The truth is that if you need to declare a variable outside your current scope you should probably declare it in the outside scope in the first place.

In the scenario with var/let I need to grok the code in order to tell which variables are visible in my current scope.

0 comments

jarekkruk6y ago

I tend to mainly use const, let only when necessary. I never use var and set linter to scream about it at me. IE11 supports it, so unless you develop application for IE compatibility mode (my condolences) I don't see a reason to use var. On the other hand var mainly bites you when declaring closures inside loops, also hoisting is just plain weird.

z3t46y ago

I find hoisting a convenient feature as I can declare the variable in context to where it's used. It means I do not have to break the flow of how the code reads, making the code easier to understand and less bug prone. Example:

    if(something) var foo = 1;

heavenlyblueOP6y ago

So how do you maintain the invariant that this variable is used only if <something> is true _down the line_?

1 more reply

j / k navigate · click thread line to collapse