tag:blogger.com,1999:blog-7840321658785378959.post8173543142801637727..comments2008-04-06T16:37:17.574+02:00muenoreply@blogger.comBlogger2125tag:blogger.com,1999:blog-7840321658785378959.post-88837342926414590622008-04-06T16:37:00.000+02:002008-04-06T16:37:00.000+02:00It's not about the language. I know Ruby, but I like Smalltalk more.<BR/><BR/>Here I talk about the behaviour, the real parallel execution of thousands of processes, and their asynchronous communication through messages and message queues.muehttp://www.blogger.com/profile/13281710981103723931noreply@blogger.comtag:blogger.com,1999:blog-7840321658785378959.post-83059089430569602142008-04-06T16:25:00.000+02:002008-04-06T16:25:00.000+02:00weird that you did not mention ruby ;)<BR/><BR/>especially .send and method_missing should give a lot of freedom to really talk only with objects therein<BR/><BR/>What about the Io language?<BR/>I think its syntax is worse than ruby, but it has one really huge idea going for it - prototypes (plus that it has very few keywords)<BR/><BR/>Its kinda like modelling your objects without the need to make a class first, and then clone from that class<BR/><BR/>BTW i think if one does not mind Erlang's syntax (i mind, but i am a bad programmer anyway) then the syntax of Io is appealing even moreAnonymousnoreply@blogger.com