Smalltalk
From APIDesign
(Difference between revisions)
| Line 1: | Line 1: | ||
Dissatisfied with relational or [[OOP]] mappings of the real world? Let's create our own world inside a computer. Let's write in [[wikipedia::Smalltalk|Smalltalk]]! | Dissatisfied with relational or [[OOP]] mappings of the real world? Let's create our own world inside a computer. Let's write in [[wikipedia::Smalltalk|Smalltalk]]! | ||
| - | I don't like that each [[Smalltalk]] system ends up being completely unique, as it is common to add new and new methods to the base Object. Usually things like isInteger, isString, etc. This is not [[API]]s | + | I don't like that each [[Smalltalk]] system ends up being completely unique, as it is common to add new and new methods to the base Object. Usually things like isInteger, isString, etc. This is not how [[API]]s should be designed, as that prevents merge of systems developed independently, imho. |
However I like [[Smalltalk]]'s [[Hotswap]]. Long time ago [[Smalltalk]] could do things [[Java]] is still [[Hotswap|dreaming about]]. | However I like [[Smalltalk]]'s [[Hotswap]]. Long time ago [[Smalltalk]] could do things [[Java]] is still [[Hotswap|dreaming about]]. | ||
Revision as of 21:29, 1 July 2011
Dissatisfied with relational or OOP mappings of the real world? Let's create our own world inside a computer. Let's write in Smalltalk!
I don't like that each Smalltalk system ends up being completely unique, as it is common to add new and new methods to the base Object. Usually things like isInteger, isString, etc. This is not how APIs should be designed, as that prevents merge of systems developed independently, imho.
However I like Smalltalk's Hotswap. Long time ago Smalltalk could do things Java is still dreaming about.
Follow
