4 ms·
> It's just that they run into situations time and time again where class-based OO is a better option Can you give an example of such situation? My experience
by nadaviv 14y ago
> It's just that they run into situations time and time again where class-based OO is a better option
Can you give an example of such situation? My experience with prototype-based inheritance is quite different - I find that it can do everything that class-based inheritance can do, and more.
- tracker1 14y agoWhat's funny, is I tend to deal directly with raw JS objects as models, then use them against modules/functions. Rarely do I ever do inheritance, or reference this.* except when dealing with monad-like utilities such as jQuery or MomentJS. My life is much happier this way, it's effective and it works... Yes, it's much closer to a C-like way of dealing with libraries, but without all the messy issues like pointer logic or memory management. People need to stop trying to shove JS's triangle into a OO's round hole.