For the record, here's the reference to the above quote:
http://www.arachna.com/edu/talks/iswp/slides/non_apache_2_of_2.html
Here are my notes from reading these slides:
It would have been nice to have a breakdown of the weaknesses of tcl and AOLserver as was done for PHP on the following slide:
http://www.arachna.com/edu/talks/iswp/slides/php.html
tcl+aolserver+openacs doesn't have the PHP weaknesses as far as I understand them. Nor does the openacs api have the weaknesses outlined with java api here:
http://www.arachna.com/edu/talks/iswp/slides/servlets.html
or the perl api here:
http://www.arachna.com/edu/talks/iswp/slides/mod_perl_2_of_2.html
or mod_perl here:
http://www.arachna.com/edu/talks/iswp/slides/bob_mod_perl.html
or dbi here:
http://www.arachna.com/edu/talks/iswp/slides/bob_dbi_1_of_2.html
In fact, "they" seem interested in using PostgreSQL here:
http://www.arachna.com/edu/talks/iswp/slides/bob_dbi_2_of_2.html
Maybe this criticism of apache+mod_perl has some insight into why tcl+aolserver+openacs was not chosen: not enough of a mature "CPAN"ish tcllib?
http://www.arachna.com/edu/talks/iswp/slides/mod_perl_1_of_2.html
These comments about their future plans seem similar to some current openacs functionality (rss?) and the xlm parcer and discussions that are going on here (now) regarding xml, xslt etc:
http://www.arachna.com/edu/talks/iswp/slides/future.html
The reasons for not using ZOPE are interesting.. at least the part about ZOPE re-creating internal sw instead of integrating with other components:
http://www.arachna.com/edu/talks/iswp/slides/zope.html
My question:
Is this MASON technology similar to the "include" tag functionality in the openacs templating system?
http://www.arachna.com/edu/talks/iswp/slides/bob_mason.html