Gabriel Webb

Posted on Dec 26, 2019

Do You Still Use Var? If So Why?

#javascript #webdev #discuss

Is using the keyword var still viable in 2019/2020? What’s your use case for it? Is it only for older legacy code?

Top comments (22)

Matei Adriel • Dec 26 '19

Am I the only one who thinks const should be the only thing used?

Comment deleted

Muttsuri • Dec 26 '19

I would like to note that const doesn't provide imutability, it only protects against reassignment

Matei Adriel • Dec 27 '19

Ofcourse, const isn't enough, but it's a starting point

Comment deleted

Matei Adriel • Dec 27 '19

I'd argue you shouldn't add props to an object after you create it

Matei Adriel • Dec 26 '19

I'd argue you should never have any value change (not in the foo = bar sense of change)

Kevin • Dec 26 '19

I am genuinely interested in your thoughts here

Heiker • Dec 26 '19 • Edited

I use it. At the very least is useful for this kind of thing.

try {
  var stuff = await unsafe_stuff();
} catch (err) {
  return Promise.reject(err.message);
}

Eugene Karataev • Dec 27 '19

Why is it necessary to use var instead of let in your example? You don't access stuff variable in catch block anyway.

Heiker • Dec 27 '19

But I want to use it outside the try/catch block.

Eugene Karataev • Dec 27 '19

Just define it in the parent scope. It has extra line if compare with var, but I think this code is more obvious, because there is no implicit hoisting.

async function foo() {
  let stuff;
  try {
    stuff = await unsafe_stuff();
  } catch (err) {
    return Promise.reject(err.message);
  }
  console.log(stuff);
}

Heiker • Dec 27 '19

That is what I'm trying to avoid. And you could still do the same with var.

I choose to believe var's implicit hoisting is a feature and not a bug.

Eugene Karataev • Dec 27 '19

I agree, this is a valid use case for var if you prefer implicit hoisting.

Eugene Karataev • Dec 27 '19

I use var in devtools console, because with let/const I got Uncaught SyntaxError: Identifier 'foo' has already been declared when re-declaring a variable.

Shannon Crabill • Dec 28 '19

I use var out of habit when I'm typing something out real quick.

My older projects use so many vars.

Nishchit • Dec 28 '19

I use var in console only, It lets me redefine and assign new value :P

Kevin • Dec 26 '19

I wanted to switch, but last I ran benchmarks against it, let ran considerable slower than var.

I'll test it again after the new year.

Comment deleted

Kevin • Dec 27 '19 • Edited

Negative. Clearly measurable differences in a highly optimized environment where performance is highly critical.

*** For fun, just did some performance testing. Right now I see no notable difference in performance between let and var. Yay, because I want to use let everywhere =)

Patrik Kiss • Dec 26 '19

Yes, I use it. Like, why wouldn't I?

Ben Lovy • Dec 26 '19

Great run-through in this StackOverflow answer. They behave differently, it's important to know what the differences are. I find let clearer in almost every case, the only exception in my personal use has already been covered by other commenters - the try/catch thing doesn't really have a clean workaround using let.

View full discussion (22 comments)

DEV Community

Do You Still Use Var? If So Why?

Top comments (22)

Read next

What's a Quickie Post?

Transforming the Wall of Text: Modern Design with Glassmorphism, CSS Animations, and Typography

Axios vs Fetch: Which is Best for HTTP Requests?

AWS AppSync Events vs IoT Core