With such experience comes the realization that there are big differences between the different approaches. Some are seriously inferior to others. Some generally aren't better or worse than others. Some are obviously better in many ways.
Have you ever worked on a significantly large JavaScript-based system that has been created by many developers over the course of several years, or even a decade? I find most people that have will know what I'm talking about. Experiencing it for yourself is much better than any academic citation I could give you.
Have you ever considered that the suitability or otherwise of Javascript for huge projects might be attributed to other aspects of the language, rather than prototype based OO?
JavaScript has many, many, many other problems aside from its use of prototype-based OO. It is a truly awful language is almost every respect. But the problems caused by its broken OO system are very obvious, and the impact they have on the maintainability of JavaScript software are extremely real. Its prototype-based OO is responsible for an entire family of its issues.
Personally I find prototype based OO very powerful and easy to use, but you won't catch me saying it is "better" in any way than class based OO.
Once again, where is your proof?