named functions stored in methods?

I just said it's "unneeded" and you'll see them a lot as anonymous functions. However, having them as named functions can help certain debuggers see where the function is being called from.

For example, you could call it myDiceRollFunction like this:

var dice = {
  roll: function myDiceRollFunction(){...}
}

And console.log(dice.roll.name); and it'd print "myDiceRollFunction" however, the name attribute of a function, whilst widely implemented isn't a ECMA standard if I recall properly.

Andrew, it's in EcmaScript 2015, so the newer standard support it officially. Here's an example to test out a difference.

test = {
  meTest: function meTest(){
    console.log(meTest);
// function meTest()
  }
}

If you do this, the console will print out function meTest. If you remove it:

test = {
  meTest: function (){
    console.log(meTest);
    // Error, meTest is not defined.
  }
}

You get error, since within the anonymous closure scope, meTest doesn't exist and so on up the chain unless you have another meTest hanging around. There's not a lot of practical reasons why you would want to refer to your own function like this.

test = {
  meTest: function meTest(){
    console.log(test.meTest);
    // function meTest()
  }
}