I am not sure comparing ANY package to assessment is fair :)
That said, I just want to address the multiple CSS issue. Its not an issue at all.
Having specific CSS in a specific place makes sense. Although it does make the page load slowly.
In this case, what we really need is a tool that understands CSS. Lee started work on that (template::head) which makes OpenACS aware of the CSS/JS etc. Once OpenACS is aware of this, it can dynamcially create and cache consolidated CSS/JS files that load quickly, but still allow for modularity.
Gustaf, XoTcl code might be faster but so far its incredibly difficult for most OpenACS developers to read. Processors are cheap and programmers are expensive. As I said before, having consisten code is a goal, but so far there hasn't been any effort to produce any sort of documentation on how to USE XoTcl wisely within the OpenACS framework. Unfortunately, until that happens you'll end up doing all the work yourself.
