Function declaration is standard in other languages so I set out to find the benefits of function expressions. Here are 3 points to shed light on the situation, from least convincing to most convincing.
1. Function expressions avoid confusion. Because function declarations are hoisted and their values are actually always declared at the top of the code, it can be confusing when you put a declaration at the bottom of your code and it turns out it’s declared at run time. Having programmed in several other languages, hoisting is such standard behavior that this point did not satisfy me.
2. It looks cleaner because it’s a variable. Because a function is a variable and represents a value, it looks much better when it’s shown as “myVar;” rather than “myVar();” This is true but the function declaration itself looks cleaner and more standard to me than a function expression so I was still unsatisfied. (See update at bottom)
3. Use in conditional statements. Because we can treat a function like a variable, we want to be able to assign values to it conditionally. If you try to do this with a function declaration, your second condition will always win out because those are hoisted and defined unconditionally (despite being in a conditional statement).
With expressions, you can appropriately assign different functions to a variable depending on other conditions.
The first source below says this is the only reason you should use function expressions and every other function should be declared. While I agree with this, it seems people are leaning toward expressions so the predominant use of declarations may be a dated practice. What are some other reasons you might use function expressions or function declarations?
My second point is incorrect. If you don’t call the function (whether instantiated by declaration or expression) with a set of parens after it then it will just return the function body.