On Tuesday 05 September 2006 08:41, Dossy Shiobara wrote: > (Apologies for the long email ahead ... but, I think it's worth a quick > read.)
All very well said! I have done a number of language surveys over the years to find one that was thread-safe, fast and easy to extend. Tcl is the only one I have ever found, except for Java. Java is just too much for me to deal with, and you still lose easy access to all the C libraries that are developed. For anyone wanting to write their own network application but leverage the most code, AOLserver/Tcl can't be beat. If you want to download and install a bulletin board for your website, AOLserver isn't a great choice. Actually, it might be best to just rent web hosting and get your bbs. But this isn't why most of the AOLserver users are using AOLserver! Adding toy languages isn't going to help. (As much as we have to get real about how 'uncool' Tcl might be, we have to get real about these toy/specialized languages: they were never designed for this scale of operation.) I like the idea of an embeded JavaScript. It is obvious (or is it?) that with the isolated context, there would be no ability for this to be a server wide language, and no attempt to glue Tcl and JavaScript togeather. It sounds very much like nsproxy, as Nathan said he even worked on this idea. Anyway, if there was a push to market AOLserver, start with marketing the known long term strengths of AOLserver. Most 'choosers' of AOLserver did so because it offered a relatively clean environment for development. The market is for companies that want to produce a service and/or who plan on tending to customers who don't want to do their own development. If you try to do this development with Apache and a bunch of modules, you run the risk that, first, your product will look unoriginal and second, that someone could easily copy it (and third or zeroth: it takes too long to develop or doesn't integrate well, so it never takes off). tom jackson -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
