Named functions vs Functions as variables in JavaScript

Wesley Smith — Mon, 29 Jan 2018 04:28:50 +0000

Took a quick 10m google to find a debate on this idea, but wasn't able to find anything.

So really, which is more readable to you:

This? (named function)

function foo (bar) {
    //some code
}

Or this? (function as a variable)

const foo = bar => {
    //some code
}

Keep in mind having other variables in the same scope along with these functions and trying to debug it!

Personally, where I currently work, we keep a strict concern about the main script functions (ones not inside of a scope) to be what I called named functions. I've been with the team for ~6 months, and we've had people who originally argue for functions as variables change their stance to that named functions are more readable.

What's your stance?

DEV Community: Wesley Smith

Named functions vs Functions as variables in JavaScript