&gt;&gt; Prototypes are flexible. They don’t have all the ceremony that’s behind
class-based OOP. In that sense, they’re fun to use. But they don’t scale well
for larger applications and that’s why people jump straight to classes.<p>Yeah, well, unfortunately class-based OOP (as the article puts it) also doesn&#x27;t
scale that well, as anyone would know who&#x27;s had to work on a 10+ years old
codebase written in Java or C# (the typical big-OOP languages). That&#x27;s why you
can google &#x27;dependency injection&#x27; and get some 2,180,000 results. Because even
with all the big-OOP you can get, scaling up and maintaining a project long-term
is pain.<p>Btw, I&#x27;ve mostly worked with C# and it&#x27;s not that I like javascript particularly (I 
mostly hate it and left to my own devices I&#x27;d use Prolog everywhere) but the whole 
OOP thing just sucks so badly. There must have been a better way to use Dr Minsky&#x27;s 
great idea [1], what we got now is no good.<p>[1] <a href="https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Frame_%28artificial_intelligence%29" rel="nofollow">https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Frame_%28artificial_intelligen...</a>