The fact is, most of the IT industry is firmly settled on class-based OOP. Prototype-based OOP is a very hard sell, even though it’s been around for nearly 30 years (since the introduction of the Self programming language). Most developers intuitively sense that prototype-based OOP does not scale well for large applications. No wonder ECMA added classes to ES6 under pressure from the IT community. And TypeScript has been gaining in popularity precisely because people want class-based OOP.
Even if you do adopt object prototypes in your application, how would you explore and maintain all the object relationships?
Perhaps you can go through your code, line by line, following the trail of object creation. Without a handy tool (akin to a class browser) to aid you, you’d have to meticulously document all the object relationships in your application. Sounds like fun, doesn’t it?
James Mickens, a Harvard professor of computer science, has an amusing tale to tell you: