My point in response was that OACS has two main parts: core and add on packages. But besides the core 'code', there is a framework, or way of doing things which is valuable. There is a higher level framework for add on packages which I mostly disagree with but it is not necessary for me to use it. If someone were to develop a blogging package which handled all the configuration and customization details, they would not have to change any core features. Users would not need to know Tcl or even know that the system was written in Tcl. These are irrelevant details. I doubt very much that a change in the OACS core or changing to xoTcl would somehow help write the eventual killer app. And in any case, it could be done right now. But if your customers want PHP or MySQL, no amount of change here will help, and if they only care about how the app works, the language and platform should be unimportant.
If you really know Tcl and OACS, you must know that writing an app will be faster with these tools than with PHP, but maybe not fast for a marketable product. These things don't write themselves. Remodeling your kitchen doesn't improve your cooking skills.
