IIRC when I looked at xotcl, it also required a hack to handle the namespace problem. It's not really so much a problem with [incr] tcl or xotcl, as it is a problem with the single-threaded design of tcl that has been shoe-horned into the multi-threaded aolserver environment. I think both modules could be modified so that the namespace problem would be transparent to end-users that wished to use them with aolserver.
Using an OO programing language in aolserver can certainly lead to more obfusication, but it doesn't have to. Certainly, you don't have to look far to find examples of incredibly obfuscated tcl code...
