Classes are premature optimization, forcing the programmer to freeze method implementations and often memory layouts during the design stage in order to make things easier for the compiler writer. Classes are also accidental complexity forcing the programmer to deal with rules and limits unrelated to the problem domain, and sometimes expend extra effort working around the class system. This talk will gaze into the soul of object oriented programming to see why classes might not always be beneficial (though they often are). We’ll look at alternate visions from the hard core classlessness of Self to the modern renaissance of Javascript. Finally, there will be a review of patterns for the proper application classless patterns.
- Date: 2010-10-15
- Location: Strange Loop
- Classes are Premature Optimation (video at InfoQ) (Looks like they used the 20-minute version of the slides. You might want to download below and follow along.)
- Classes are Premature Optimization (pdf of slides; 6.4MB)
- Justin Love’s prototypal bookmarks on Delicious See also oop
