attempting to tie together similar but distinct disciplines / domains / whatever. I never did class _or_ prototype object oriented programming but I go over the concepts now and again. With a tiny bit more under my belt, the distinctions here are clicking a bit better than they might have a few years ago. [this is a 1996 paper] “The distinction between class-based and prototype-based systems reflects a longlasting philosophical dispute concerning the representation of abstractions. Plato viewed forms — stable, abstract, “ideal” descriptions of things — as having an existence more real than instances of those things in the real world. Class-based languages such as Smalltalk, C++ or Simula are Platonic in their explicit use of classes to represent similarity among collections of objects. Prototype-based systems such as Self [UnS87], Omega [Bla91, Bla94], Kevo [Tai92, Tai93], GlyphicScript [Gly94] and NewtonScript [SLS94] represent another view of the world, in which one does not rely so much on advance categorization and classification, but rather tries to make the concepts in the problem domain as tangible and intuitive as possible. A typical argument in favor of prototypes is that people seem to be a lot better at dealing with specific examples first, then generalizing from them, than they are at absorbing general abstract principles first and later applying them in particular cases ” Classes vs. Prototypes Some Philosophical and Historical Observations 1996 http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.56.4713&rep=rep1&type=pdf

attempting to tie together similar but distinct disciplines / domains / whatever. I never did class _or_ prototype object oriented programming but I go over the concepts now and again. With a tiny bit more under my belt, the distinctions here are clicking a bit better than they might have a few years ago. [this is a 1996 paper]
 
“The distinction between class-based and prototype-based systems reflects a longlasting philosophical dispute concerning the representation of abstractions. Plato viewed forms — stable, abstract, “ideal” descriptions of things — as having an existence more real than instances of those things in the real world. Class-based languages such as Smalltalk, C++ or Simula are Platonic in their explicit use of classes to represent similarity among collections of objects. Prototype-based systems such as Self [UnS87], Omega [Bla91, Bla94], Kevo [Tai92, Tai93], GlyphicScript [Gly94] and NewtonScript [SLS94] represent another view of the world, in which one does not rely so much on advance categorization and classification, but rather tries to make the concepts in the problem domain as tangible and intuitive as possible. A typical argument in favor of prototypes is that people seem to be a lot better at dealing with specific examples first, then generalizing from them, than they are at absorbing general abstract principles first and later applying them in particular cases “
 
Classes vs. Prototypes
Some Philosophical and Historical Observations
1996
 
http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.56.4713&rep=rep1&type=pdf

Leave a comment

Your email address will not be published. Required fields are marked *


8 − seven =

Leave a Reply