Most of the time, a script needs to work with information. If it’s an online-shop – that’s going to be the goods and a shopping cart. If it’s a chat – users, messages and so on.
Variables are used to store the information.
A variable is a “named storage” for data. We can use variables to store goodies, visitors and other data.
The statement below creates (in other words: declares or defines) a variable with the name “message”:
Now we can put some data into it by using the assignment operator
let message; message = 'Hello'; // store the string
The string is now saved into the memory area associated with the variable. We can access it using the variable name:
To be concise we can merge the variable declaration and assignment into a single line:
We can also declare multiple variables in one line:
let user = 'John', age = 25, message = 'Hello';
That might seem shorter, but it’s not recommended. For the sake of better readability, please use a single line per variable.
The multiline variant is a bit longer, but easier to read:
let user = 'John'; let age = 25; let message = 'Hello';
Some people also write many variables like that:
let user = 'John', age = 25, message = 'Hello';
…Or even in the “comma-first” style:
let user = 'John' , age = 25 , message = 'Hello';
Technically, all these variants do the same. So, it’s a matter of personal taste and aesthetics.
In older scripts you may also find another keyword:
var instead of
var message = 'Hello';
var keyword is almost the same as
let. It also declares a variable, but in a slightly different, “old-school” fashion.
There are subtle differences between
var, but they do not matter for us yet. We’ll cover them in detail later, in the chapter The old "var".
We can easily grasp the concept of a “variable” if we imagine it as a “box” for data, with a unique-named sticker on it.
For instance, the variable
message can be imagined as a box labelled
"message" with the value
"Hello!" in it:
We can put any value into the box.
Also we can change it. The value can be changed as many times as needed:
When the value is changed, the old data is removed from the variable:
We can also declare two variables and copy data from one into the other.
In such languages, once the value is stored “in the box” – it’s there forever. If we need to store something else – the language forces to create a new box (declare a new variable), we can’t reuse the old one.
Though it may seem a little bit odd at first sight, these languages are quite capable of serious development. More than that, there are areas like parallel computations where this limitation confers certain benefits. Studying of such a language (even if not planning to use it soon) is recommended to broaden the mind.
- The name must contain only letters, digits, symbols
- The first character must not be a digit.
Valid names, for instance:
let userName; let test123;
When the name contains multiple words, camelCase is commonly used. That is: words go one after another, each word starts with a capital letter:
What’s interesting – the dollar sign
'$' and the underscore
'_' also can be used in names. They are regular symbols, just like letters, without any special meaning.
These names are valid:
Examples of incorrect variable names:
let 1a; // cannot start with a digit let my-name; // a hyphen '-' is not allowed in the name
AppLE – are two different variables.
It is possible to use any language, including cyrillic letters or even hieroglyphs, like this:
let имя = '...'; let 我 = '...';
Technically, there is no error here, such names are allowed, but there is an international tradition to use English in variable names. Even if we’re writing a small script, it may have a long life ahead. People from other countries may need to read it some time.
There is a list of reserved words, which cannot be used as variable names, because they are used by the language itself.
For example, words
function are reserved.
The code below gives a syntax error:
Normally, we need to define a variable before using it. But in the old times, it was technically possible to create a variable by a mere assignment of the value, without
let. This still works now if we don’t put
use strict, the behavior is kept for compatibility with old scripts.
That’s a bad practice, it gives an error in the strict mode:
To declare a constant (unchanging) variable, one can use
const instead of
const myBirthday = '18.04.1982';
The variable declared using
const are called “constants”. They can not be changed. An attempt to do it would cause an error:
When a programmer is sure that the variable should never change, he can use
const to guarantee it, and also to clearly show that fact to everyone.
There is a widespread practice to use constants as aliases for difficult-to-remember values that are known prior to execution.
Such constants are named using capitals and underscores.
COLOR_ORANGEis much easier to remember than
- It is much easier to mistype in
- When reading the code –
COLOR_ORANGEis much more meaningful than
When should we use capitals for a constant, and when – name them normally? Let’s make that clear.
Being a “constant” just means that the value never changes. But there are constants that are known prior to execution (like a hexadecimal value for red), and there are those that are calculated in run-time, during the execution, but do not change after the assignment.
const pageLoadTime = /* time taken by a webpage to load */;
The value of
pageLoadTime is not known prior to the page load, so it’s named normally. But it’s still a constant, because it doesn’t change after assignment.
In other words, capital-named constants are only used as aliases for “hard-coded” values.
Talking about variables, there’s one more extremely important thing.
Please name the variables sensibly. Take time to think if needed.
Variable naming is one of the most important and complex skills in programming. A quick glance at variable names can reveal which code is written by a beginner and which by an experienced developer.
In a real project, most of the time is spent on modifying and extending the existing code base, rather than writing something completely separate from the scratch. And when we return to the code after some time of doing something else, it’s much easier to find the information that is well-labelled. Or, in other words, when the variables have good names.
Please spend some time thinking about the right name for a variable before declaring it. That will repay you a lot.
Some good-to-follow rules are:
- Use human-readable names like
- Stay away from abbreviations or short names like
c, unless you really know what you’re doing.
- Make the name maximally descriptive and concise. Examples of bad names are
value. Such a name says nothing. It is only ok to use them if it’s exceptionally obvious from the context which data or value is meant.
- Agree on terms within the team and in your own mind. If a site visitor is called a “user” then we should name related variables like
newUser, but not
Sounds simple? Indeed it is, but creating good descriptive-and-concise names in practice is not. Go for it.
And the last note. There are some lazy programmers who, instead of declaring a new variable, tend to reuse the existing ones.
As the result, the variable is like a box where people throw different things without changing the sticker. What is inside it now? Who knows… We need to come closer and check.
Such a programmer saves a little bit on variable declaration, but loses ten times more on debugging the code.
An extra variable is good, not evil.
We can declare variables to store data. That can be done using
let– is a modern variable declaration. The code must be in strict mode to use
letin Chrome (V8).
var– is an old-school variable declaration. Normally we don’t use it at all, but we’ll cover subtle differences from
letin the chapter The old "var", just in case if you’ll need them.
const– is like
let, but the value of variable can’t be changed.
Variables should be named in a way that allows to easily understand what’s inside.