I don't think making a hash table of closures is necessarily equivalent to "object orientation". Sure, if you use a set of well-known keys to represent an inte

I don't think making a hash table of closures is necessarily equivalent to "object orientation". Sure, if you use a set of well-known keys to represent an interface, then it's headed that way. But the same structure can be used for other things, e.g. a table of opaque IDs to closures encapsulating a possible "next step" through a workflow in an interactive program. Indeed, I think the original news.arc did exactly that in many places (and contemporary Hacker News still does somewhat?). (My reading of the "wimpier languages" bit was that it was probably a dig at Java, where [prior to Java 8], you had to explicitly write an inner class to emulate a closure...)