Skip to main content

The ever so common var, let and const

 So in JavaScript world, in whichever way you go, you finally end up with some very basic concepts.

 

I skipped certain basics while learning JavaScript. Later in life, I regretted it, but then, of course, you don't repeat the same mistake twice.


So the very common and pretty basic thing you could see in JavaScript is the concept of var, let and const.

 

What are they? How do they differ from each other?

 

Simply put var, let and const are keywords within JavaScript.


All three of them are used to declare a variable. So why do we need three of them?


JavaScript is weird. You can even use a variable without initialization in JavaScript. So why take the time to write a keyword.


Now for JavaScript, there is a concept called global scope. In a simple browser where you could see JavaScript quite common, the global scope refers to the window object. And in the NodeJs module, this will be the global scope of the module.

So if you simply don't initialize a variable JavaScript looks at the global scope, even though you never even thought about scoping your variable globally.


So these keywords do matter then. 

But which one to use.


var

var is function scoped, and even if you tried to call it after the initialization you get the value as undefined.

 

console.log(hoisted)

var hoisted


The above code will be interpreted by the engine as below:

 

var hoisted 

console.log(hoisted) 

 

So the output that you are going to get is simply undefined. 


let

in case of let, it's all about block scoped. So everything inside a block stays inside.

Also in case of the above code, we run for var will be converted reversely, but unlike var giving you an undefined, now you'll get a reference error

 

const

In the case of const, it's pretty simple. you cannot re-assign values to a variable that you initialized using const. And also they are block-scoped.



So which one to use.


There are many theories and many styles. But I use let and const. 

Some people do initialize with const first then upon situation were they need to re-initialize the variables, they change the code to make it initialized using let.

 

So which one are you going to use? I know this is pretty simple, and not much explained, but basically, this will help you get started with the weird way of JavaScript.


Thanks

Comments

Popular posts from this blog

A smoooooth operation....

 Backward compatibility...   A word that I used to hear when I started my career. You design your APIs with backward compatibility in mind, don't break anything when you are upgrading, think about this, think about that etc. Well, those teachings from my previous mentors didn't go in vain, as I made a fundamental change in how we report problems @  Gelato .    You see recently @  Gelato , the CS (Customer Support) team moved from A ticketing management system to B ticketing management system, which is a monumental task for all the people involved in the CS team. Even though the fundamental concept remains the same the places, the attributes the concepts, and the naming of different attributes all change if you have this transition. And thus it was a big change for the whole company.    After the decision was taken, the first step was to create a well-written transition document, which the good folks at the CS team tackled. Special thanks to  ...

My experience with the Golden signals

In June 2022, I embarked on a quest for a new job opportunity. Fortunately, this endeavor began just before the global job market experienced a significant downturn. I must admit, I faced my fair share of rejections during this period, but I also had an epiphany. It became evident that there was so much more to learn and understand in the world of technology. Coming from a small service-based company, I had encountered limitations in terms of how much I could learn on the job. However, during interviews and conversations with senior developers, I gained valuable insights into the architectural and technical decisions made by teams in various companies. One such company that left a lasting impression on me was Delivery Hero. Their technical blog posts provided a wealth of information, especially for someone like me, transitioning from a smaller company where projects had minimal daily active users compared to the scale of Delivery Hero. One particular blog post that caught my attention ...

AI. Will it replace us or...?

AI!! The buzzword is too hot in the market nowadays. Do you have a technical product or an idea? If it doesn't have AI in it, then chances are it's not going to be sold like hot cakes. That is how things have changed lately. It is no wonder why me and my colleagues at Gelato want to see what AI can do in a niche department like customer support and service. And that is exactly what we did. For a company like Gelato, which is in the market for production-on-demand, there are a lot of customer questions you need to answer. It can be related to products, queries about shipping and pricing, and so on and so forth. Thus, our customer support team is always happy to help with these recurring questions. Let's take one example. A customer asked us, "Do you ship to Norway?" Now that is an easy question to answer if you have the knowledge written somewhere where you could refer to it and say, "Yes! As a matter of fact, we do." Following the same thread, the next q...