Home/ Questions/Q 89813
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-10T22:46:31+00:00

I come from classes object orientation languages and recently I have been learning those

  • 0

I come from classes object orientation languages and recently I have been learning those fancy dynamic languages (JavaScript, Python and Lua) and I want some tips about how to use OO in those languages. It would be useful to know the pitfalls and the shortcomings of such approach and the advantages compared to traditional OO.

The general notion that I got is that prototype based OO is basically programming with objects but no standard on how to use them whereas in normal OO there is a fixed predefined way to make and use objects.

In summary, what is the good, the bad and the ugly parts of such approach?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Prototype-based OO lends itself poorly to static type checking, which some might consider a bad or ugly thing. Prototype-based OO does have a standard way of creating new objects, you clone and modify existing objects. You can also build factories, etc.

    I think what people like most (the ‘good’) is that prototype-based OO is very lightweight and flexible, offering a very high power-to-weight ratio.

    For tips on how to use prototype-based OO, a great place to start is the original Self paper on The Power of Simplicity.

    • 0