On Fri, October 26, 2007 4:38 pm, Andrew Lentvorski wrote: > Tracy R Reed wrote: >> James G. Sack (jim) wrote: >>> I don't have any experience with ruby, but it certainly has an active >>> and enthusiastic community, which gives it a lot of significance. >> >> I haven't really looked at Ruby much other than read some reviews >> because it just doesn't seem different enough from any other programming >> language which I am already familiar with. > > Bingo. > > If I couldn't use Python, I'd probably go look at Ruby. Although, I > would probably give Tcl another look, too. The problem Tcl had was that > it was so grubby and unstable in the timeframe that I needed something > other than Perl (Tcl 8.0) that I went and learned Python. It is no > longer grubby and unstable, but I've already learned one scripting > language and have no need to learn a similar one. > > In order to replace Python, the next language I learn will have to > handle concurrency elegantly. > > Right now, none of the scripting languages handle concurrency right. > Stackless Python is probably closest, but really needs to get a JVM port > for me to believe that they've got it. > > Erlang has possibilities, but it's libraries suck and it is too wedded > to its C implementation. Gambit with Termite also looks interesting and > is retargetable. Scala's implementation of Actors looks okay and runs > on the JVM. > > Nothing compelling has yet broken through, really. > > -a
I write this w/o even really knowing what concurrency means, but Tcl has threads. However, the Tcl gurus say, "if you think you need threads in Tcl, you almost certainly are wrong." IOW, that there is an easier way to do whatever it is in Tcl. Again, I cannot assess this. I'm so far from needing threads that I don't even need to know what it means (lucky me!) :-) -- Lan Barnes SCM Analyst Linux Guy Tcl/Tk Enthusiast Biodiesel Brewer -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
