Why to use class based OOP style inheritance in javascript? -
If I am not completely wrong then every framework / library / approach in JavaScript today is to remove class based OOP style legacy Goes for The reason for this is that people who understand Class-based OOP heritage are very easy to understand and that most programmers know OOP
In my experience, I do not find the evidence for both of this opinion. That Javascript prototype legacy is just fine (and I suspect it's utility to force another paradigm on one language compared to a built-in language). Most developers I am getting from are not good at the classical OOP. So what are the reasons for choosing a classical OOP style legacy on prototype legacy?
I think the answer is in your question - the comparison of prototype-based with most programmer class-based OOP Are more familiar with
In fact, I can say that majority believe that you can not object without classes.
Comments
Post a Comment