为什么要在这里使用箭头函数而不是类或对象构造函数？

Question

I'm working on a small project, mainly to help teach myself JavaScript, and I have a question about a suggestion someone had.

My goal is to have a list of races and rpg classes that when I create a new character object I can assign it a race and an rpg class that it will gain the attributes of.

Here's my method and my reasoning behind it. I'm using a class to define the objects (I'm pretty sure is what I'm doing) that way I can create functions for those classes/objects to do things. Like on the Player class I can then create functions that manage the Player's inventory. and when I instantiate a new player I can assign them a race object and an rpg class object.

class Orc {
  constructor() {
    this.mortal = true
  }
}

class Player {
  constructor(race, name, level){
    var inventory = {};
    this.race = race;
    this.name = name;
    this.level = level;
    this.inventory = inventory;
    this.currentCapacity = 0;
    this.maxCapacity = 50;
  }
}

const orc = new Player(new Orc(), 'Baz', 1 )
console.log(orc.race)

And here's the method I was suggested to use:

const raceTemplates = {
  human: { mortal: true }, 
  elf: { mortal: true }
}

const playerMaker = template => (race, name, level) => {
  return {
    name,
    level,
    race,
    inventory: {},
    currentCapacity: 0,
    maxCapacity: 50,
    ...template[race]
  }
}  

const player = playerMaker(raceTemplates)('elf', 'sammy', 2)
console.log(player) 

I'm relatively new to JavaScript and I've seen the Arrow Functions before however I'm pretty much entirely self taught so the theory of why some things are better than others is where I fall short on. I think I understand what Arrow Functions are but as I've said I'm new to JavaScript and self taught (have PluralSight course offerings through work that I've used) so I'm not too familiar with them.

Any help is appreciated and if this isn't a good question or it's already been answered I apologize. Thank you!

Answer 1

Of course this is opinionated, but to me a "classic" formulation of:

function playerMaker(template,race,name,level){
...
}

Would be clearer for someone reading it. The arrow syntax is just syntax sugar to not write "function". But here, creating a nested function that is returned from the master function to be invoked later seems both unintuitive and inefficient to me, in lack of any example where it would be useful as written.

Answer 2

Reasons not to use Classes in Javascript:

1. The concept of “Class” doesn't exist in JavaScript.

   • JavaScript classes, introduced in ECMAScript 2015, are primarily syntactical sugar over JavaScript's existing prototype-based inheritance. The class syntax does not introduce a new object-oriented inheritance model to JavaScript.

2. Concept of classes makes things brittle. Prototypes are better and very flexible (IMO, although I still will use them from time to time).
3. It guides people away from goodness and power of functional programming.
   • In JS functions are first-class citizens. Functional programming is all about using functions to their fullest extent. There is a notion called: “Favor Composition over Inheritance” and here we are going in the opposite direction because “Class” notation favors “Inheritance over Composition”.