DEV Community

Cover image for JavaScript’s Arrow Functions Explained By Going Down A Slide
Kevin Kononenko
Kevin Kononenko

Posted on

JavaScript’s Arrow Functions Explained By Going Down A Slide

If you have been using JavaScript for a few years, you are probably familiar with this syntax:

function addTen(num){
  return num + 10;
});

console.log(addTen(10));
//20
Enter fullscreen mode Exit fullscreen mode

This function syntax was popular in ES5, or ECMAScript 5.

There is one major advantage to this syntax: It includes the word function, so it is obvious that you are writing a function!

A function clearly takes in anywhere from 0 to many arguments and runs a specific set of statements every time that it is called.

But then the world of JavaScript took a leap forward with ES6 in 2015.

Now, the same function as above would be written like this:

let addTen = (num) => num + 10;

console.log(addTen(10));
//20
Enter fullscreen mode Exit fullscreen mode

Now, there is no function keyword, and no return statement! Functions in ES6 are much more terse , or concise.

So, since those obvious clues have been removed, you might be having a little bit of a hard time with understanding the different parts of arrow functions.

Fortunately, as you will soon see with a few animations, arrow functions are pretty easy to understand once you learn to visualize the arrow “=>” in a new way.

So here is how arrow functions are just like a water slide. In order to fully understand this tutorial, it might help to know about map functions and scoping.

Arrow Functions Visualized

Let’s explore the addTen function a little more deeply.

let addTen = (num) => num + 10;

console.log(addTen(10));
//20
Enter fullscreen mode Exit fullscreen mode

This function will transform one parameter and output that parameter with 10 added.

The transformation happens with that subtle “=>” arrow.

It can also be written with a return statement:

let addTen = (num) => {return num + 10};

console.log(addTen(10));
//20
Enter fullscreen mode Exit fullscreen mode

I like to transform that arrow into a tube slide in my mind to show what is actually happening. Here is what I mean:

The equals sign is like the tube slide and the arrow is like the landing pad.

Arrow functions follow this pattern:

(parameters) => {statements}

So let’s add those to the diagram with our addTen function example.

The last thing we need to show is how the parameter, which is 10 in this case, goes down the slide and becomes available in the statements of the function. Here’s what that looks like.

That’s all it is! Pretty straightforward.

Now, let’s look at an example where there are two different parameters. Here is our new function:

let multiply = (num1, num2) => {return num1 * num2};

console.log(multiply(2, 10));
//20
Enter fullscreen mode Exit fullscreen mode

In this case we are just multiplying the two parameters together. Both will go down the slide together. Like this:

There’s one more example you should know about- combining the map() method with arrow functions.

The map() method will send every element in an array into the arrow function, in order.

Let’s go through an example- imagine that you have an array of numbers, and you want to get the square root of each one.

Here’s the code.

let nums = [1, 4, 9];

let squares = nums.map((num) => {
  return Math.sqrt(num);
});

console.log (squares)
// [1, 2, 3]
Enter fullscreen mode Exit fullscreen mode

You need to know a little about the map method to understand this one. But, you will probably notice the terse syntax yet again- the map() method is much shorter than writing a for() loop.

Here’s what is happening in this code:

  1. There are three elements in the nums array, so the num parameter goes down the slide 3 times.
  2. The Math.sqrt() method takes the square root of the number each time.
  3. The result is stored in the squares array each time.

The Difference Between Arrow Functions And Traditional Functions

You might be wondering… is this simply a difference in syntax?

Actually, there is one important way that the traditional ES5 functions and ES6 functions work differently.

The big change is that arrow functions do not have their own scope. Therefore, if you try to use the this keyword, you will be surprised when it does not refer to the scope of the arrow function.

To go back to our slide analogy, this means that this is the same at the top and bottom of the slide. If we were using ES5 functions, then this would be different at the top and bottom of the slide.

To quickly recognize this in code, just look for the function keyword. If you see it, that means that a new scope is being created. If not, assume that you are using the scope of the enclosing function.

Interested In More Visual Tutorials?

If you would like to read more visual tutorials about HTML, CSS and JavaScript, check out the main CodeAnalogies site for 50+ tutorials.

Top comments (9)

Collapse
 
gusgonnet profile image
Gustavo

this is great, amusing and easy to understand!
I now see slides all over my code :)
love it

Collapse
 
kbk0125 profile image
Kevin Kononenko

Thanks Gustavo :)

Collapse
 
misterbrash profile image
MisterBrash

Maybe I read it too fast or I'm too tired but I don't see where you explain why there's no return keyword in your first arrow function example...

Collapse
 
dirkkiesewetter profile image
Dirk Kiesewetter

Arrow functions can have implicit returns: dev.to/samanthaming/es6-arrow-func...

Collapse
 
misterbrash profile image
MisterBrash

Many thanks to both of you. Great article.

Collapse
 
kbk0125 profile image
Kevin Kononenko

Hey, Dirk is correct with his comment about implicit returns. But, for the sake of clarity, I added another code block showing the same function using the return keyword!

Collapse
 
geocine profile image
Aivan Monceller • Edited

This is really nice way of explaining it. However my OCD is killing me , I was expecting the parameters to be animated as they slide down to the landing pad. Still great post!

Collapse
 
mauri profile image
Mauri

xD Same over here :P

Collapse
 
tchaflich profile image
Thomas C. Haflich

It is very difficult for me to not make "wheeee" sound effects while reading this article.

Thank you.