Re:Why Every Ruby Developer Should Learn Smalltalk
by angersock on Tuesday April 17, 2012 @04:53PM
(#3854937)
What sort of issues did you observe with concurrency and Smalltalk?
[ Parent
| on HN ]
Re:Why Every Ruby Developer Should Learn Smalltalk
by stcredzero on Tuesday April 17, 2012 @05:24PM
(#3855066)
All the usual ones. You could very well hose your image. The nice thing, though, is that you could just kill your process, restart the image, and recover all of your code changes.
You could also have a Smalltalk "Process" (or green thread) starve the other ones. Lots of Smalltalks are single-threaded. VisualWorks is too, but has tricks for calling out to DLLs with a separate thread.
Re:Why Every Ruby Developer Should Learn Smalltalk
by bitops on Tuesday April 17, 2012 @08:34PM
(#3855781)
Do you have a twitter account or blog? I'd love to follow you if yes.
Re:Why Every Ruby Developer Should Learn Smalltalk
by stcredzero on Tuesday April 17, 2012 @09:10PM
(#3855923)
Currently, the best place to follow me is in HN comments. I plan to restart my blog soon.