From: Stephen D. <sd...@gm...> - 2006-09-18 20:59:45
|
On 9/18/06, Zoran Vasiljevic <zv...@ar...> wrote: > > On 18.09.2006, at 19:58, Stephen Deasey wrote: > > > > > > > Are you running a fever? > > Ah no! I'm just trying to see what others think. > Well, all responses so far were not exactly > in favour of that but that doesn't matter. > I'm not going to start working on that in short > nor in mid term. But, this MIGHT ease newbie > acceptance, don't you think? > After all, Netscape did that already some years > ago.... So it is not just out of the blue... > Yeah, and how popular are the Netscape servers? Tcl sucks, that's for sure. But it rules in these three very important areas: * It's thread safe (and thread friendly) * It's utf-8 safe * You can write domain specific languages in it. I think it's the last point which makes up for the suckage, and which is also the main selling point of Ruby. When you wite a Rails application, what you end up with *looks* like it does what it does -- a python program always seem to look like just another python program. People are writing a lot of sucky Tcl for AOLserver. Here's an example from a couple of days ago: proc startworker {name} { nsv_set $name mutex [ns_mutex create] nsv_set $name cond [ns_cond create] nsv_set $name queue {} nsv_set $name tid [ns_thread begindetached [list workermain $name]] } Jumping through hoops with low level mutexes and and variables etc., you see it all the time. Why can't we have code that looks like this? ns_serialize { # Only one copy of this code runs at a time } Which brings us back to nsproxy and handle management... :-) |