I attended FutureRuby in Toronto and wanted to give a the local ChicagoRuby a group a review.
It seems like very often when someone writes about prototypal inheritance in Javascript, the first thing they try to do is make it behave like a C/Java style classical inheritance system. I put together a talk for JS.chi to go over some of the ways I've used prototypal inheritance in it's native form.
During one of the ChicagoRuby meetings there was a question about lambda. Since I tend to be interested in language details like that, I thought I might be able to offer a little education
The kind organizers of Ruby Hoedown have given me 45 minutes to expand on Lambda and Closure talk given previously. It mostly went into some IRB sessions, and covering the odd difference between blocks and lambdas in a little more detail.
This will be a 20-minute neigh-lighting talk version, leaving no room for fluff whatsoever.
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.
It's only 20 minute slot, so the agenda might get trimmed a little once the talk starts taking shape.