> > In Smalltalk it is more readable and you hardly notice the difference to > the normal Smalltalk code, while in JavaScript those callbacks are a bit > hard to grasp and understand.
+1 2011/6/30 Janko Mivšek <[email protected]> > S, Norbert Hartl piše: > > > Am 30.06.2011 um 17:23 schrieb Stéphane Ducasse: > > >>>> apparently people get excited by nodeJS and I would like to know the > equivalence of > > >>> What does it mean? > > >> in Pharo.. how do you have the same: > > > It depends what is in your head when you wrote this. The code snippet > doesn't tell that much. Registering a Block for execution on request is > probably not what makes you excited about. What is exciting about it is that > javascript is written in a strictly asynchronous manner (event driven) and > that matches perfectly the implementation with asynchronous I/O. Suddenly > you can write programs they way you ever wanted it. And lucky for us > smalltalk itself is event driven so it can go there easily, too. Well, > easily would mean to have support for asynchronous I/O in the vm (file > operations) and in the socket plugin at least. > > Because I'm just working on asynchronous no-blocking node.js like > control flow in Aida, I can say that this is really natural to Smalltalk > with its closures, much more than so called callbacks in JavaScript. In > Smalltalk it is more readable and you hardly notice the difference to > the normal Smalltalk code, while in JavaScript those callbacks are a bit > hard to grasp and understand. From non seasoned programmer perspective, > that is. > > Best regards > Janko > > -- > Janko Mivšek > Aida/Web > Smalltalk Web Application Server > http://www.aidaweb.si > >
