Ruby and objective c are both strongly influenced by small talk. Yes. That’s on the right track. I’d say messages are very loosely coupled compared to a functi

Ruby and objective c are both strongly influenced by small talk. Yes. That’s on the right track. I’d say messages are very loosely coupled compared to a function or method call. In c everything is laid out by the linker. You can play games with function pointers, of course, but that is tricky. Message passing isn’t really resolved till the message is actually sent. Late binding I think it’s called. Objective c gives so much control, you could add remoting at dispatch time. I think Java’s methodinvoker is pretty much it for Java. You can implement an interface at runtime. But you don’t control dispatch quite as deeply. Micro services approximate some of Kay’s ideas really well, but imho they give up too much control over dispatch. In ruby or objective c you can hijack the dispatch system in a way that’s really hard to do with micro services