I think there are good reasons why classes have been introduced in ES6, so you can use both, a prototype based approach and a class based approach today.
Classes contain data and procedures (called methods), so, inside, a class features a procedural approach(in fact, we are using functions, but as the term "functional programming" is already occupied, the classical approach often is called "procedural"). Often, it is a very natural transistion from procedureal code to class based OO.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I think there are good reasons why classes have been introduced in ES6, so you can use both, a prototype based approach and a class based approach today.
Classes contain data and procedures (called methods), so, inside, a class features a procedural approach (in fact, we are using functions, but as the term "functional programming" is already occupied, the classical approach often is called "procedural"). Often, it is a very natural transistion from procedureal code to class based OO.